Skip to content
DT Nova

Agile vs waterfall: the differences, the trade-offs and how to choose

Agile vs waterfall is the choice between planning a whole project up front and running it in sequential phases (waterfall), or delivering working software in short cycles and adjusting the plan as you learn (agile). This guide defines both, compares them side by side, lists the pros and cons, shows where Scrum, Kanban and hybrid models fit, explains what each means for contracts and budgets, and gives a short test for your project.

The short version

  • Waterfall: fixed scope, sequential phases, testing near the end, change is costly.
  • Agile: short cycles, working software early, scope adapts, change is expected.
  • Waterfall suits stable, well-specified work; agile suits uncertainty.
  • Scrum and Kanban are agile frameworks, not alternatives to agile.
  • Most real projects use a hybrid: a planned frame with agile delivery inside.

Definitions

Waterfall is a sequential approach: requirements are gathered and signed off, then the system is designed, built, tested and released, each phase starting when the previous one ends. Progress is measured against the plan, and documents carry the knowledge from one phase to the next. Our guide to software development methodologies covers its history and the V-model variant.

Agile is a family of approaches based on the Manifesto for Agile Software Development (2001), which values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan, while recognising value in the items on the right. Its principles put "early and continuous delivery of valuable software" first and welcome changing requirements, even late in development.

Agile vs waterfall side by side

AspectWaterfallAgile
PlanningDetailed plan up frontHigh-level goal, detail planned each cycle
ScopeFixed at the startAdapts as the team learns
DeliveryOne release at the endWorking increments every few weeks
TestingA phase near the endContinuous, in every cycle
Customer roleSigns off requirements and acceptanceReviews each increment and sets priorities
ChangeFormal change requests, costly lateExpected; reprioritised in the backlog
DocumentationExtensive, phase by phaseEnough to build, run and maintain
Main riskBuilding the wrong thing wellDrifting scope and budget without discipline

Pros and cons of waterfall

  • Pro: a clear plan, budget and end date that sponsors and procurement understand.
  • Pro: thorough documentation, useful for regulated systems and handovers.
  • Pro: works when requirements are stable and well understood, such as a migration or an integration to a published standard.
  • Con: users see the system late, so misunderstandings surface when they are most expensive to fix.
  • Con: testing squeezed at the end when earlier phases overrun.
  • Con: changes in the market or business during the project are hard to absorb.

Pros and cons of agile

  • Pro: working software early, so value and feedback start in weeks.
  • Pro: risk is found sooner, because every cycle is built and tested.
  • Pro: priorities can change without rewriting the whole plan.
  • Con: the final scope and cost are less certain at the start.
  • Con: it needs a customer representative who is available and can decide.
  • Con: without a clear goal and a definition of done, it turns into a stream of small changes.

Where Scrum, Kanban and hybrid fit

Scrum is the most widely known agile framework. The Scrum Guide (November 2020 version) describes Sprints as fixed-length events of one month or less, with planning, daily coordination, a review of the increment and a retrospective inside each one.

Kanban visualises work on a board, limits work in progress and pulls new items when capacity frees up, without fixed cycles. It suits maintenance and support teams with a steady flow of requests; see software maintenance.

Hybrid approaches plan phases with a scope, budget and milestones, and build inside each phase in agile iterations. They are common in client projects because they give a known budget per phase and still show working software early.

Contracts and budgets

The method and the contract must match. A fixed price for the whole product assumes waterfall-style fixed scope; trying to work agile inside it leads to arguments about every change. Agile fits time and materials, or fixed prices per short phase with a written rule for changes. Our guide to fixed price vs time and materials covers the options, and a good software requirements specification helps with either method.

How to choose: a six-question test

  1. Can you write the requirements today, and will they still be right in six months?
  2. Is the scope fixed by a law, a standard or a tender that cannot change?
  3. Will real users be available to review work every few weeks?
  4. Is it more costly to deliver late or to deliver the wrong thing?
  5. Does the budget holder need one total figure, or can they approve phase by phase?
  6. Can the system be released in useful parts, or only as a whole?

Mostly "yes, fixed, no, late, one figure, whole" points to waterfall. Mostly the opposite points to agile. A mix, which is the most common answer, points to a hybrid.

How we run projects

We use the hybrid on client projects: each phase has a written scope and a fixed price agreed before work starts, and inside the phase we work in short iterations, showing working software on your own data at the end of each. The source code sits in your company's own repository from day one. For how this plays out on a build, see custom software development; for budgets, the guide to custom software development cost; and for apps, agile mobile app development. Every guide is in the guides library.

Questions people ask

What is the main difference between agile and waterfall?

Waterfall plans the whole project up front and runs it in sequential phases: requirements, design, build, test, release. Agile delivers working software in short cycles and adjusts the plan after each one based on what users and the business learn. Waterfall fixes the scope and lets time and cost absorb surprises; agile fixes time and cost per cycle and lets the scope adapt.

Is Scrum agile or waterfall?

Scrum is an agile framework. The Scrum Guide describes it as a lightweight framework for generating value through adaptive solutions for complex problems, with work done in Sprints, fixed-length events of one month or less, each ending with a usable increment that is reviewed with stakeholders.

Which is better, agile or waterfall?

Neither is better in general. Waterfall suits projects with stable, well-understood requirements, fixed regulatory or contract scope and expensive changes late on. Agile suits products where users' needs are uncertain, the market moves, or early feedback is valuable. Most software projects today combine both: a planned frame with agile delivery inside it.

What is a hybrid of agile and waterfall?

A hybrid plans the project in phases with a written scope, budget and milestones, as waterfall does, and builds each phase in short agile iterations with working software reviewed at the end of each. It gives sponsors a known budget per phase and gives the team room to adjust the details.

Can a fixed-price project be agile?

Yes, if the fixed price applies to a defined phase rather than the whole product, and the contract says how changes are handled, for example by swapping items of similar size or moving them to the next phase. Our guide to fixed price vs time and materials explains the contract side.

Sources