Waterfall Project Management: Phases, Pros, Cons, and When to Use It

Waterfall Project Management: Phases, Pros, Cons, and When to Use It

Waterfall project management is a linear, sequential approach in which a team completes each phase before the next begins. The 5 phases are requirements, design, implementation, testing, and maintenance. Waterfall fits projects with fixed requirements, strict regulation, and low expected change.

Waterfall is the best-known predictive approach. Construction, aerospace, manufacturing, and government contracting run on it. Software teams use it when requirements stay stable. This article covers the phases, 6 pros, 6 cons, a comparison with Agile, and a 6-factor test for when to use it.

What is waterfall project management?

Waterfall project management is a predictive methodology that plans the full scope, schedule, and cost upfront, then executes in strict sequence. Each phase ends at a gate with a signed-off deliverable. Work flows downward and does not return to earlier phases.

Four attributes define waterfall:

• Sequence: 5 phases run in a fixed order.
• Phase gates: a formal approval closes each phase.
• Documentation: requirements, design specs, and test plans are written before build work starts.
• Baselines: scope, schedule, and cost are locked at planning and changed only through formal change control.

The approach belongs to the predictive family in PMI vocabulary. A project manager uses a Gantt chart, a work breakdown structure (WBS), and critical path analysis to plan and track it.

Where did the waterfall model come from?

Herbert Benington presented the phased development approach for SAGE software in 1956. Winston Royce published the first detailed diagram in 1970. Bell and Thayer used the term “waterfall” in a 1976 paper, the earliest known use.

Royce’s 1970 paper, “Managing the Development of Large Software Systems,” shows 7 steps: system requirements, software requirements, analysis, program design, coding, testing, and operations. Royce did not endorse a pure one-way flow. He wrote that the implementation he described was “risky and invites failure.” His revised diagrams loop back to earlier steps, and he recommended a pilot model and customer involvement.

The U.S. Department of Defense adopted the model in DOD-STD-2167 in 1985 and moved away from it in MIL-STD-498 in 1994. The pure sequential version spread through government contracting. The iterative warnings in Royce’s paper did not.

What are the phases of waterfall project management?

Waterfall has 5 phases: requirements, design, implementation, testing, and maintenance. Each phase produces a defined deliverable and closes at a gate. The next phase starts only after approval.

Phase	What happens	Key deliverables	Gate question
1. Requirements	The team collects and documents every requirement and sets scope	Requirements specification, scope statement, WBS	Is the scope complete and signed off?
2. Design	Architects translate requirements into system, interface, and data designs	Design documents, architecture diagrams, test plan	Does the design cover every requirement?
3. Implementation	The team builds components, tests units, and integrates modules	Code, built components, integrated system	Is the build complete against the design?
4. Testing	QA runs functional, performance, regression, and user acceptance testing (UAT)	Test reports, defect log, acceptance sign-off	Does the product pass acceptance criteria?
5. Maintenance	The team deploys, trains users, fixes defects, and tunes performance	Deployed system, user manuals, support plan	Is the product accepted into operations?

PMI’s process groups (initiating, planning, executing, monitoring and controlling, closing) run across these phases. Planning dominates phases 1 and 2. Executing dominates phases 3 and 4. Closing happens at the end of phase 5.

What are the advantages of waterfall project management?

Waterfall has 6 advantages: clear structure, firm milestones, detailed documentation, predictable cost, easy progress tracking, and compliance support. Each advantage comes from planning everything upfront and freezing the baseline.

• Clear structure: every team member knows the phase, the owner, and the deliverable.
• Firm milestones: gates give sponsors measurable checkpoints, such as design approval.
• Detailed documentation: written specs let new members join mid-project and support audits.
• Predictable cost and schedule: a locked scope produces estimates that a sponsor signs and a PMO tracks.
• Easy progress tracking: a Gantt chart with dependencies and baselines shows variance every week.
• Compliance support: regulated industries need traceability from requirement to test result.

What are the disadvantages of waterfall project management?

Waterfall has 6 disadvantages: rigidity, late testing, delayed customer visibility, heavy upfront planning, costly changes, and poor fit for uncertainty. Each disadvantage comes from the same source: the team cannot return to an earlier phase cheaply.

• Rigidity: a change request after the baseline needs formal approval and re-planning.
• Late testing: defects surface in phase 4, after the build is complete.
• Delayed customer visibility: clients see working output near the end, so misalignment appears late.
• Heavy upfront planning: requirements and design work delays visible progress.
• Costly changes: the later a change arrives, the more rework it triggers across design and build.
• Poor fit for uncertainty: products in fast-moving markets become outdated before delivery.

When should you use waterfall project management?

Use waterfall when requirements are fixed, the scope is well understood, regulation demands documentation, and change is expensive or dangerous. Construction, manufacturing, aerospace, defense, government, and pharmaceutical projects fit this profile.

Score the project against these 6 factors:

1. Confirm that requirements are stable and signed off before work starts.
2. Check that the deliverable is physical or irreversible, such as a bridge, a plant, or hardware.
3. Verify that regulators or contracts require phase approvals and traceability.
4. Assess that the team has delivered similar projects, so estimates rest on history.
5. Confirm that the sponsor wants a fixed price, fixed scope, and fixed date.
6. Review that customers do not need to see working output before the end.

Examples by industry:

• Construction: the foundation precedes framing, and framing precedes electrical work. A skyscraper or bridge cannot iterate its foundation.
• Manufacturing: an automotive line locks tooling and design before production starts.
• Aerospace and defense: military equipment follows phase gates and formal reviews.
• Pharmaceuticals: drug development passes phased approvals before manufacturing.
• Software with stable requirements: legacy system migrations and embedded systems fit when the specification does not move.

Avoid waterfall for products with unclear requirements, short market windows, or heavy customer feedback loops. Those projects favor an adaptive approach.

What is the difference between waterfall and agile?

Waterfall plans everything upfront and delivers once at the end. Agile plans in short cycles and delivers working increments every 1 to 4 weeks. Waterfall controls change. Agile welcomes change.

Attribute	Waterfall	Agile
Approach	Predictive, sequential	Adaptive, iterative
Planning	Full plan upfront	Rolling plan per iteration
Requirements	Fixed at the start	Evolve through the backlog
Delivery	One release at the end	Working increments each sprint
Customer involvement	At gates	Continuous
Change handling	Formal change control	Reprioritized backlog
Documentation	Extensive	Lean
Best fit	Regulated, physical, high-cost-of-change work	Software, innovation, uncertain scope

Many organizations blend the 2. A fixed-budget plan with iterative delivery is the hybrid pattern. Read how teams move between them in the transition from waterfall to agile guide.

How does waterfall appear on the PMP exam?

The PMP exam tests waterfall as the predictive approach. Candidates identify when a predictive life cycle fits, how change control works, and how phase gates, baselines, and the WBS apply. About 60% of the 2026 exam sits in agile and hybrid contexts.

The remaining questions test predictive scenarios. A scenario with fixed scope, signed contracts, and regulatory sign-offs points to waterfall. A scenario with shifting requirements points away from it. Review how the traditional process groups map onto a predictive life cycle before exam day.

Test the judgment with scenario questions. The PMP certification practice test from Project Management Training Institute includes predictive, agile, and hybrid cases in exam format.