Home › The Garage › Agile vs waterfall
Transformation

Agile vs waterfall

Waterfall plans the whole thing, then builds it. Agile builds a slice, learns, and adjusts. Neither is “right” — the honest question is how much you actually know up front, and how costly it is to be wrong.

By LeanBean · Updated November 2026 · 6 min read
What's in this guide
  1. Two shapes of delivery
  2. When waterfall fits
  3. When agile fits
  4. Choosing honestly
  5. Common questions
Waterfall Plan Design Build Test Release Agile Cycle 1working slice Cycle 2working slice Cycle 3working slice Waterfall delivers once at the end; agile delivers a working increment every cycle and adjusts.
Waterfall sequences the whole plan; agile repeats short cycles, each producing something usable.

Two shapes of delivery

Waterfall runs the work as one sequence — plan, design, build, test, release — each phase finished before the next begins. Agile runs many short cycles, each producing a working increment you can inspect and learn from, with the plan adjusted as you go. The deep difference is when you decide: waterfall decides most things up front; agile defers decisions until it has learned enough to make them well.

When waterfall fits

Waterfall earns its keep when the requirements are well understood and stable, the cost of change late is high, and the sequence is genuinely fixed — regulated construction, hardware with long lead times, work with hard compliance gates. Here, planning thoroughly up front is not bureaucracy; it is cheaper than discovering a structural problem after you’ve built on top of it.

When agile fits

Agile earns its keep when there is genuine uncertainty — you don’t fully know what’s needed, the market or users may teach you something, and the cost of a small wrong step is low. Delivering a slice, getting feedback and adjusting beats committing to a detailed plan built on guesses. Most software and most transformation work lives here.

Choosing honestly

The question is uncertainty, not fashion
Don’t pick by what’s fashionable or what the last project used. Ask: how much do we really know up front, and how expensive is it to be wrong? High certainty and costly late change lean waterfall; high uncertainty and cheap iteration lean agile. Many real programmes are hybrid — a planned backbone with agile delivery inside it — and that is a legitimate answer, not a fudge.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

The Garage — a community of practice

The Garage is where Lean, process and AI-readiness practitioners learn in the open — short lessons, real examples, and a place to compare notes. Join the community: follow along, try it on your own work, and share what you find.

Common questions

What is the main difference between agile and waterfall?

Waterfall completes the work as one planned sequence of phases, deciding most things up front. Agile runs short repeated cycles, each producing a working increment, and defers decisions until it has learned enough. The core difference is when decisions are made.

When is waterfall the better choice?

When requirements are well understood and stable, the cost of changing things late is high, and the sequence is genuinely fixed — as in regulated construction or hardware. Thorough up-front planning is then cheaper than discovering a problem after building on it.

When is agile the better choice?

When there is real uncertainty about what is needed, feedback can teach you something, and a small wrong step is cheap to correct. Delivering a slice and adjusting beats committing to a detailed plan built on guesses, which is why most software and transformation work suits it.

Can you combine agile and waterfall?

Yes. Many programmes use a planned backbone — fixed milestones or compliance gates — with agile delivery inside it. A hybrid is a legitimate choice when parts of the work are certain and parts are not.

Related guides: Scrum & Kanban for delivery · Work decomposition · Change management