Waterfall Project Management

Waterfall project management runs a project as a fixed sequence of phases. Each phase ends at a gate, and the next one cannot start until that gate is signed, so plans are set up front and change is handled as a formal request.

The classic phase list is requirements, design, implementation, verification and maintenance. Each phase produces a document or a build that the following phase treats as settled input.

The model is older than its name. Winston Royce’s 1970 paper, “Managing the Development of Large Software Systems”, drew the diagram everyone still copies, and it is widely reported to warn against a single pass through the sequence rather than to recommend one.

Sequential delivery has not gone away. It still wins where scope genuinely cannot move — regulated submissions, physical build, hardware, and migrations tied to a fixed cutover date.

Key takeaways

• Waterfall moves work through requirements, design, implementation, verification and maintenance in one direction.
• A phase gate, not a calendar date, is what lets a project move to the next stage.
• Royce’s 1970 paper is far more often cited than read, and it is commonly credited with a warning the model ignored.
• The cost of changing a decision rises the later it is discovered, which is the real argument against long phases.
• Fixed scope, regulated evidence and physical deliverables are where sequential delivery still beats the alternatives.

How it works

Work moves through the phases in one direction. Each phase has entry conditions, a deliverable and an exit review, and that review decides whether the project proceeds, reworks the phase, or stops entirely before more money is committed.

Formal gates are not unique to software. NASA’s Software Engineering Handbook publishes entrance and exit criteria for each life cycle review, including the review materials a project must table before it is allowed to pass.

The trade-off is feedback timing. The UK government’s service manual notes that agile shortens feedback loops compared with waterfall, where feedback is only sought once the final product is complete.

That is the cost-of-change curve in plain terms. A misread requirement costs an edit in week two, a redesign in month six, and a rebuild after launch — the same mistake, priced three different ways.

Change control — formal, costed and approved — is the pressure valve. Once a phase is signed, new scope arrives as a change request with its own estimate, approval and budget line rather than as a conversation.

Verification sits near the end, which is why acceptance testing carries so much weight in a sequential plan. The detail of how that stage runs belongs to its own entry.

Roles harden under a sequential plan. Analysts finish before designers start, designers finish before builders start, and each handover is a dated document rather than a standing conversation.

Planning tools match the shape. A critical path method schedule assumes known tasks and known dependencies, which is exactly what a signed design gives you.

Examples

Sequential delivery survives in settings where the deliverable is physical, the evidence is audited, or the date is immovable. Four cases show why a team would choose phases and gates over iteration, and what they give up in exchange.

A pharmaceutical manufacturer building a regulated batch-records system documents requirements, design and verification as separate validated stages. The audit trail is the point, and a regulator expects to see each stage signed.

An infrastructure contractor pouring concrete cannot iterate the foundations, not cheaply anyway. Design is finished, approved and priced before anyone breaks ground, and a late change means demolition rather than a redeploy.

A payroll migration with a 1 January cutover runs backwards from the date. Parallel runs sit in the verification phase, and the gate before cutover is a go or no-go decision taken by named executives.

A defence programme buying hardware and software together ties payment to milestone acceptance, which is why milestone-based pricing and sequential phases tend to travel in the same contract.

Related terms

Waterfall brings a whole vocabulary of plans, gates and baselines with it. The entries below cover the scheduling tools, governance bodies and commercial structures that sit alongside a sequential delivery plan in most organisations.

• Project Management Triangle: the scope, time and cost trade-off a fixed plan has to balance.
• Gantt Chart: the bar schedule used to show phase durations and dependencies.
• Project Management Office: the function that sets delivery standards and reviews gate decisions.
• Agile Outsourcing: the iterative alternative, contracted around capacity instead of a fixed scope.
• Software Development Outsourcing: the practice of contracting build work to an external provider under either model.

FAQ

What are the phases of waterfall project management?

Requirements, design, implementation, verification and maintenance. Variants add feasibility or deployment phases, but the one-directional flow and the gate between each phase stay the same.

Did Winston Royce invent the waterfall model?

His 1970 paper carried the diagram that became the model, though he did not use the word waterfall. The paper is usually cited as advocating the sequence, which is not how most readers of the full text describe it.

When is waterfall better than agile?

When scope is genuinely fixed and change is expensive: regulated systems, physical construction, hardware, and migrations with a hard cutover date.

What is a phase gate?

A formal review at a phase boundary with documented entry and exit criteria. The project proceeds only if the gate’s conditions are met and someone with authority signs.

Can waterfall and agile be combined?

Many organisations run a sequential outer frame around iterative build work, so that funding and compliance follow gates while the team still delivers in increments.

Explore the Outsource Accelerator site for more on how delivery models shape outsourced projects.