What it is
Waterfall is the classic predictive, plan-driven approach: the project moves through sequential phases — requirements, design, build, test, deploy — each completed before the next begins, like water flowing down a series of steps. Scope is fixed early, and the plan is the contract. Agile is an adaptive, iterative approach: work is delivered in short cycles (often two-week sprints), each producing a working increment, with requirements expected to evolve as stakeholders see and react to real output. Agile is an umbrella for frameworks such as Scrum and Kanban, all rooted in the values of the Agile Manifesto (individuals and interactions, working software, customer collaboration, responding to change).
Between the two sits the hybrid model, which uses predictive governance at the programme level and iterative delivery inside it. The European Commission's Agile PM² is exactly this: PM²'s phase gates and governance wrap around Scrum-style sprints.
How it works in practice
The two models differ on four things that matter.
1. Requirements and scope. Waterfall locks scope at the start and treats changes as exceptions managed through formal change control. Agile keeps a prioritised product backlog and expects scope to be refined every sprint, fixing time and cost while letting scope flex.
2. Delivery cadence. Waterfall delivers value once, at the end. Agile delivers a usable increment every iteration, so stakeholders get working output — and a chance to course-correct — early and often.
3. Roles. Waterfall has a project manager directing the plan. Scrum replaces that with a Product Owner (owns the backlog and priorities), a Scrum Master (removes impediments, protects the process) and a self-organising development team.
4. Risk and feedback. Waterfall pushes integration and testing late, so big risks surface late. Agile front-loads feedback through sprint reviews and retrospectives, surfacing risk continuously — at the cost of less certainty about the final scope up front.
| Dimension | Waterfall (predictive) | Agile (adaptive) |
|---|---|---|
| Requirements | Fixed up front | Evolve via the backlog |
| What's fixed | Scope | Time & cost (scope flexes) |
| Delivery | One release at the end | Increment every sprint |
| Feedback | Late (after testing) | Continuous (each iteration) |
| Best when | Requirements stable, compliance-heavy | Requirements uncertain, fast-moving |
| Main risk | Late discovery of wrong assumptions | Scope creep / unclear end state |
For EU work the choice is rarely absolute. A regulated infrastructure rollout with fixed legal requirements suits a predictive plan; a citizen-facing digital service whose needs are still forming suits Agile. This is why the Commission's Agile PM² exists: it keeps PM²'s business case, steering committee and phase gates — the accountability an EU project needs — while letting the build team work in sprints. The governance is predictive; the delivery is iterative.
Common points of confusion
- Agile is not "no planning." Agile plans constantly — it just plans in smaller increments and re-plans every sprint. The myth that Agile means no documentation or no plan is the single most common misconception.
- Scrum is not a synonym for Agile. Agile is the set of values and principles; Scrum and Kanban are specific frameworks that implement them. You can be Agile without using Scrum.
- Hybrid is not "doing both badly." Wrapping iterative delivery in predictive governance (Agile PM²) is a deliberate, recognised model — not a failure to commit to one approach.
Why it matters for EU project managers
Choosing the delivery approach is one of the first real decisions a project manager makes, and getting it wrong wastes months. For EPSO/AD/429/26 Field 2 (ICT Project Management), expect questions that give you a scenario — stable legal requirements versus an evolving digital product — and ask which approach fits, or that probe Scrum roles and events, or that test whether you understand how Agile PM² reconciles governance with iteration. The exam rewards judgement about when each model applies. Build that judgement with the full study pack: Prep for AD7 ICT Project Management on Prep4EU