Agile, Waterfall or Hybrid — Choose Your Model

"We run Agile" is a phrase you hear often today — but Agile is not a universal tool. Just as a skilled craftsman selects the right tool for the job, a competent project manager should choose the method that fits the nature of the project, the organisation, and the risk profile.

Waterfall: Structure and predictability

The Waterfall method is linear and sequential: requirements are fully defined before development begins, and the project moves through fixed phases one step at a time. It is the right approach when requirements are stable and well-defined, when there are strict regulatory requirements for documentation, or when the project has many dependencies on other systems and processes. Examples: ERP implementations, compliance projects, infrastructure replacements.

Agile: Flexibility and rapid feedback

Agile methods — including Scrum and SAFe — work in short iterations (sprints) and prioritise continuous feedback and adaptation. They are ideal for projects where requirements are not fully known from the start, where user involvement is central, or where the market moves quickly. However, Agile requires active and engaged stakeholders and an organisation ready for continuous change.

Hybrid: The best of both worlds

In practice, most complex IT projects are neither purely Waterfall nor purely Agile. A hybrid approach combines the structured planning and governance of Waterfall with the flexibility and iterative development of Agile. The overall project plan and milestones are managed in a Waterfall-like manner, while the actual solution development runs in agile sprints. This is particularly effective in larger transformation projects with many stakeholders.

How to choose

Three questions help you make the right choice: (1) Are requirements stable and well-defined? Yes → Waterfall or hybrid. No → Agile. (2) Can the organisation handle continuous change? Yes → Agile. No → Waterfall. (3) Are there strict requirements for documentation and traceability? Yes → Waterfall as a minimum for the governance layer. Remember: the method is a means, not an end. What matters most is that it serves the project — not the other way around.

The We Lead Projects approach

We are method-neutral. We assess each project individually and recommend the approach that fits your specific situation. Our consultants have experience with all three models and can guide you — whether you are in the process of selecting a methodology or need help breaking free from a rigid project model.

Brian P.N. Tofft

Managing Partner, We Lead Projects