When it comes to delivering digital projects, organisations often look for the perfect methodology.
Should you use Agile? Waterfall? Scrum? Kanban?
The answer is rarely as simple as choosing one.
Every digital project is different. It has different levels of complexity, different stakeholders, different technologies, different dependencies and different levels of risk and uncertainty. Trying to force every project into a single methodology can create unnecessary friction and, in some cases, become the very reason a project fails to deliver.
The most effective approach is often not choosing one methodology. It is creating your own delivery model, combining the right elements of different approaches to suit the project in front of you.
Start With the Project, Not the Methodology
Methodologies are frameworks. They are not the objective. The objective is to deliver a successful outcome within the preset budget and timeframe. Some parts of a digital project may require detailed planning and clear sequential stages. Others may involve experimentation, learning and continuous iteration. Treating both in exactly the same way rarely makes sense.
For example, infrastructure, governance, security and major technical dependencies may require a more structured, waterfall-style approach. These areas often need clear requirements, approvals and sequencing before the next stage can begin.
But customer journeys, user interfaces and digital experiences may benefit from a more agile way of working. You can test, learn, refine and improve based on feedback. Rather than asking which methodology is best, ask which way of working is best for each part of the project.
Combine Waterfall and Agile Where They Make Sense
A hybrid approach allows organisations to bring structure and flexibility together.
Waterfall can provide the discipline needed to manage budgets, governance, dependencies and major milestones. Agile can provide the flexibility needed to respond to changing requirements and customer feedback. The key is understanding where each approach adds value.
You may need a clear long-term roadmap and a defined set of project outcomes. At the same time, you may not know exactly what the final customer experience should look like until you begin testing it.
That is not a contradiction. It is the reality of digital transformation.
A successful delivery model should give teams enough structure to maintain control, while creating enough flexibility to learn and adapt.
Take Baby Steps Instead of Attempting a Big Bang
One of the biggest mistakes in digital projects is trying to change everything at once.
The “big bang” approach can look attractive. Launch everything on one date. Replace the old system. Introduce every feature. Transform the entire experience. In reality, big bang projects create significant risk.
The more you try to deliver at the same time, the more dependencies you create. Testing becomes more complex. Problems become harder to isolate. Teams are placed under greater pressure. And when something goes wrong, the impact can be significant.
A more effective approach is to break the journey into smaller, manageable steps.
Start with the highest-priority problem. Launch a minimum viable solution. Learn from real users. Fix what is not working. Build on what is. Smaller releases reduce risk and allow you to create value earlier, rather than waiting until the entire transformation is complete.
Build Learning Into the Delivery Model
Digital projects should not simply be managed. They should be designed to learn. Every release is an opportunity to gather insight. What are users doing? What are they ignoring? Where are they experiencing friction? Which features are creating value? What assumptions turned out to be wrong?
This is why an effective methodology needs more than project plans and deadlines. It needs feedback loops.
You need regular opportunities to test assumptions, review performance and change direction when necessary. The faster you learn, the faster you can improve and the less time and money you spend investing in the wrong solution.
Create Your Own Playbook
The goal is not to invent a completely new methodology. It is to create a practical playbook that works for your organisation and your projects.
That playbook might include:
- Waterfall planning for major dependencies and governance
- Agile sprints for product and experience development
- Clear decision gates for investment and risk management
- Small releases rather than one major launch
- Regular customer and stakeholder feedback
- Continuous testing and optimisation
- A roadmap that provides direction without preventing change
Your methodology becomes a tool that supports delivery rather than a rigid process that teams have to work around.
The Best Methodology Is the One That Helps You Move Forward
Experience taught us that there is no single methodology that works for every digital project.
Digital transformation is rarely predictable enough for pure waterfall and often too complex for an entirely unstructured agile approach. The answer is not to choose sides. Take the best elements of different methodologies and apply them where they make sense. Plan where you need certainty. Experiment where you need to learn. Deliver in manageable steps. Measure what happens. Then improve.
Most importantly, avoid the temptation to wait for the perfect moment to launch everything.
Our founder Clayton J Zammit believes that “Progress beats perfection. Small, controlled steps help you learn, reduce risk and build momentum, while a big bang can leave your entire project exposed.”
The best methodology is not the one you read about in a textbook. It is the one you build around the realities of your project and the one that helps your organisation keep moving forward.
