For a decade, agile and waterfall were presented as opposing camps, one modern and enlightened, the other outdated and rigid. That framing always served rhetoric better than reality. Both are legitimate approaches to organizing work, each strong under conditions that expose the weakness of the other.
The practical question facing delivery leaders is not which philosophy to adopt but which approach — or which blend — suits the specific work in front of them. Answering it well requires understanding what each approach assumes about the nature of that work.
What waterfall assumes
Waterfall — a sequential approach moving through defined phases of requirements, design, build, test, and deploy — assumes that the work can be understood and specified upfront. When that assumption holds, waterfall is powerful: it offers predictability, clear milestones, straightforward contracting, and the ability to commit to scope, cost, and date with confidence.
The approach fits domains where requirements are stable and well understood, where change is expensive, and where predictability is prized — construction, infrastructure, manufacturing, and regulated delivery. Its weakness appears when the upfront assumption is false: when requirements are uncertain, waterfall discovers its mistakes late and corrects them expensively.
What agile assumes
Agile assumes the opposite: that requirements will evolve, that early certainty is an illusion, and that value is best delivered incrementally with continuous feedback. Under conditions of genuine uncertainty, this is a profound advantage — the approach surfaces misunderstandings quickly and cheaply, and steers towards value as understanding grows.
Agile fits software, product development, and innovation, where the destination is genuinely discovered en route. Its cost is predictability: fixing scope, budget, and date simultaneously runs against its grain, which is precisely why it sits uneasily with traditional fixed-price contracting.
Designing a hybrid that works
Most substantial initiatives contain both kinds of work, which is why hybrid delivery has become the default in mature organizations. The art of hybrid design is to apply each approach where it is strong rather than blending them into an incoherent compromise.
- Govern the overall program with stage-based control, giving leadership predictable decision points and financial oversight.
- Deliver uncertain, evolving workstreams — software, design, innovation — with agile iterations inside that governance.
- Keep stable, well-defined workstreams — infrastructure, procurement, regulatory — on a plan-driven track.
- Define clearly how the two interact: how agile progress is reported into stage gates, and how dependencies are managed across tracks.
The failure mode to avoid
The worst outcome is a hybrid in name only — an organization that adopts agile ceremonies while retaining a fixed, upfront plan and refusing to let requirements change, or one that abandons all planning discipline in the name of agility. Both take the costs of an approach without its benefits. A genuine hybrid is designed deliberately, with each approach given the conditions it needs to succeed.
Agile and waterfall are not beliefs to choose between. They are instruments to deploy — and the skilled delivery leader plays both.
Key takeaways
- 1Waterfall suits stable, well-understood work where predictability is prized.
- 2Agile suits uncertain, evolving work where value is discovered incrementally.
- 3Most real initiatives contain both, making deliberate hybrid delivery the practical default.
- 4Design hybrids so each approach gets the conditions it needs — avoid incoherent compromise.
Frequently asked questions
Is waterfall obsolete?
Not at all. For construction, infrastructure, and other domains with stable requirements and a need for predictability, a plan-driven approach remains the right tool. Obsolescence is a myth; misapplication is the real problem.
How do you contract for agile work?
Through models that price capacity and value rather than fixed scope — time-and-materials, capped time-and-materials, or outcome-based arrangements — often within a governance framework that preserves financial control.
