ICB® Individual Competence Baseline
How Do Agile and Waterfall Differ in Project Management?
The difference between Agile and Waterfall in project management lies in how the output is delivered. Waterfall develops linearly and puts everything into use at the end of the project. Agile works iteratively and incrementally, delivering in a series of small steps with close collaboration between developers and users.
What is the Waterfall approach in project management?
Waterfall is the traditional approach in which the output is developed linearly and put into use entirely at the end of the project. Work moves through the project step by step, and users receive the result only once everything is complete. In Waterfall, scope and quality are set in advance.
In Project Management by ICB4 – IPMA by Bert Hedeman and Roel Riepma, this contrast is covered under "Agile versus Waterfall" in the chapter on Project Orientation. Because scope and quality are fixed up front, the project manager's attention goes to controlling time and costs.
What is the Agile approach in project management?
Agile is a conceptual approach to implementing changes iteratively and incrementally. Iterative means products are developed cyclically; incremental means the output is delivered in a series of small steps. Developers and users work closely together from the start, so users see results during the project instead of only at the end.
The book puts it this way: "The advantage of Agile projects is that developers and users work closely together from the start." The approach was formalised in 2001 in the Manifesto for Agile Software Development, and it is worked out further in the section on Development Frameworks.
The book describes this as the opposite of the traditional Waterfall approach, where nothing is put into use until the end.
How do Agile and Waterfall differ in scope, time and cost?
In traditional Waterfall projects, scope and quality are set and the effort goes into controlling time and costs. Agile projects turn this around: they are driven by the number of features delivered within a predetermined period. The underlying attitude is to accept that the customer doesn't need everything.
| Aspect | Waterfall | Agile |
|---|---|---|
| Development | Linear | Iterative and incremental |
| Delivery | The entire output is put into use at the end | Output is delivered in a series of small steps |
| Scope and quality | Set in advance | Driven by the number of features delivered |
| Time and costs | Controlled during the project | Fixed in a predetermined period |
The book's phrase "Accept that the customer doesn't need everything" captures the shift. Instead of promising the full scope, an Agile team delivers as many features as fit within the available period.
When is Agile a better fit than Waterfall?
Agile fits any project where strong collaboration with users is required and incremental delivery is an option. Where close cooperation between developers and users matters, an Agile approach delivers benefits. In such projects the change authority is usually delegated to a product owner.
The book therefore names two conditions: strong collaboration with users and the possibility of delivering in steps. If the output cannot be delivered incrementally, the second condition is not met. In that case the linear logic of Waterfall is the contrast the book offers.
The product owner's role is a practical difference. Decisions about changes sit with a delegated person, not only with the traditional project governance.
Is it a choice between Agile or Waterfall, or something in between?
It is not a matter of 'yes or no' but of 'how much'. The book stresses that applying Agile in a project is a question of degree, so you choose how much Agile suits the project rather than switching entirely. Scrum, Kanban and Lean Six Sigma (LSS) are well-known Agile frameworks.
The book says: "Please note: applying Agile in a project is not a matter of 'yes or no'. The question is 'how much'." There are already more than 100 Agile frameworks, so the choice of framework is a decision in itself.
Scrum is a good example of how a framework adds structure. A typical Scrum team comprises ten or fewer individuals, to prevent sub-teams from emerging.
Not 'Agile or Waterfall', but 'how much Agile'
Project Management by ICB4 – IPMA presents Waterfall as linear delivery at the end and Agile as iterative, incremental delivery. The real question for your project is how much Agile fits.
Ways to learn this standard
Projectmanagement op basis van ICB versie 4 – 4de herziene druk – IPMA B, IPMA C, IPMA-D , IPMA PMO
Projectmanagement op basis van ICB4
Request a quote from a training partner
Frequently asked questions
Neither approach is shown to be better in general, because the book offers no quantitative comparison of success rates between Agile and Waterfall. It also gives no case studies with specific organisations. What it does offer is a way of choosing: look at whether strong collaboration with users is needed and whether incremental delivery is possible.
It does not describe any specific hybrid methodology or certification route beyond the ICB4 context. Instead it frames the choice as 'how much' Agile suits the project, which points to a flexible mix rather than a fixed recipe. For a named hybrid method you would need a separate source.
Scrum is one of the well-known Agile frameworks, whereas Agile itself is the broader conceptual approach to iterative and incremental change. A framework gives a team concrete structure for working this way. Kanban and Lean Six Sigma are other examples named in the book, so choosing Agile does not automatically mean choosing Scrum.
Project managers and team members who want to place Agile and Waterfall within the IPMA competence baseline will get the most from it. The book by Bert Hedeman and Roel Riepma treats the Agile versus Waterfall question in its Project Orientation chapter. The standard page on the Van Haren website is a good place to start.





