How to Adopt a Project Methodology...The Easy Way

If you've already realised you need a project methodology in your business or team, then you're already winning!

But now you're wondering which one suits your needs best. 🤷🏻♂️

Well, what if I told you that you could create your own methodology tailored to your business needs? Would that make it easier to:

Decide...
Implement... 🤔

If you answered yes, then today might just be your lucky day! 🎉

In this guide, we'll explore Agile and Waterfall project methodologies, cherry-picking elements that you can adopt easily.

However, there are many other approaches out there, so use what fits best for you.

Disclaimer:

For the project purists, please don't come at me for simplifying methodologies. My goal is to make operations and project methodologies accessible, relatable, and most importantly, easy. 🙏🏻

Man sits at laptop awkwardly — Staring at a contact us page like a pro

TL;DR:

Use scrums (stand-ups) and retrospectives at the very least.
Accept change and manage it well.
Always scope projects.
Avoid Waterfall (personal opinion).
Good day.

Agile Project Methodology

As the name suggests, Agile is about adaptability.

This iterative approach breaks projects into phases, encourages continuous improvement through retrospectives, incorporates feedback, and promotes flexibility to achieve the best possible outcome. While Agile is widely used in product development, its principles can be applied to any project.

We won't go into too much detail here, many many books do that, such as:

Key Features of Agile:

Scrum: At Opticks, a scrum is simply a stand-up where you discuss:
- What you did yesterday
- What you're doing today
- Any blockers
Feature-Driven Development: Let features drive the development process, prioritising client needs based on Agile feedback loops.
Customer Feedback Integration: Collect feedback continuously. While scope creep can be a risk, well-managed change requests make a huge difference.
Flexibility: Change is only scary if mismanaged. Agile enables adaptability while staying within budget and timeline constraints.
Lean Software Development: Keep things simple, from team structures to development processes.
Parallel Workflows: Agile allows multiple project elements to progress in parallel, optimising efficiency.

Drawbacks of Agile:

Scope Creep: Poorly managed changes can derail the project and inflate costs.
No Clear End: Continuous iteration can make it feel never-ending.
More Time & Energy Required: Project managers need to be highly engaged.
Complexity: Agile is fast-paced, flexible, and demanding.

Fun Example: Making a Cup of Tea (Agile Style)

Project Name: Making Tea for My Wife

Stakeholders: My Wife

Project Manager: Me

Scope: English Breakfast Tea, milk, no sugar

Scrum Meeting: I inform my wife that the kettle is broken. She suggests using the hob. The project scope is adjusted accordingly.
Mid-Sprint Change: My wife decides she wants mint tea instead. We submit a change request and update the timeline.
Unit Testing: Check water temperature before making the tea.
Delivery: Tea is served, but the wrong mug is used.
Retrospective: Next time, I’ll use the correct mug.

Waterfall Project Methodology

(Note: I personally dislike Waterfall, but here’s an objective breakdown.)

Waterfall is a traditional, linear project management approach where each stage must be completed before moving to the next. It works best when requirements are defined upfront and are unlikely to change.

Key Features of Waterfall:

Easier to manage and track progress.
Well-structured with clear project milestones.
Saves time and money when requirements are stable.

Drawbacks of Waterfall:

Rigid and inflexible.
Assumes no changes will occur (which is unrealistic in most cases).
Testing occurs at the end, increasing the risk of failure.

Fun Example: Making a Cup of Tea (Waterfall Style)