Skip to content
All apps

Waterfall or Agile?

About this app

The same customer portal runs twice: as a waterfall in phases and as Scrum in sprints, week by week. Event cards (new feature, change, cancellation) drop into both lanes in the same week; misunderstandings stay face down until a review or the acceptance test reveals them. Rework appears hatched, and the curves show cumulative benefit and cost up to week 40. Switches for uncertainty, sprint length, feedback and partial deliveries separate the two effects: less rework and earlier benefit.

The idea

In the waterfall model a project runs through phases one after another: requirements, design, implementation, testing, acceptance. Scrum works in short sprints, delivers increments regularly and gathers feedback in each review. The difference matters mostly when requirements are uncertain. Delivering in short iterations with feedback uncovers changes and misunderstandings while they are still cheap to fix. Partial deliveries also bring value earlier. Without uncertainty and without partial deliveries, both approaches perform the same.

What the app shows

A customer portal is built twice, on top as waterfall in phases and below as Scrum in sprints, week by week. Event cards such as new features, changes or cancellations land in both lanes in the same week. Misunderstandings stay hidden until a review or acceptance reveals them. Rework is shown hatched. Below, curves show cumulative value and cost up to week 40. The numbers are a model, not a forecast: the mechanism is the point.

Try it yourself

Set uncertainty to “none”: there are no event cards and both curves coincide. Raise uncertainty step by step and compare rework and value. In the Scrum part, toggle review feedback and partial deliveries separately to tell the two effects apart: less rework from early feedback and earlier value from partial deliveries. Sprint length can be set from one to four weeks.

Frequently asked questions

What is the difference between waterfall and Scrum?
The waterfall model plans a project in consecutive phases and delivers at the end. Scrum works iteratively in short sprints, delivers increments regularly and adjusts the plan after every review. Scrum therefore responds faster to changing requirements.
When is agile better than waterfall?
Mainly when requirements are uncertain or change. Early feedback exposes misunderstandings before much is built on them, and partial deliveries bring value sooner. If requirements are stable and fully known, the advantage is small.
Why is late rework so expensive?
The later a misunderstanding is discovered, the more work has been built on it and must be changed. In waterfall many errors only show up at acceptance. In short iterations they appear earlier, while the fix is still small.
What can I adjust in the simulation?
The uncertainty of requirements (none to high), sprint length from one to four weeks, and whether there is review feedback and partial delivery. The simulation runs step by step or automatically.

Subject: Software engineering

More from Software engineering

A VisuApp by heyprof: interactive, free in your browser, no sign-up. What is a VisuApp? · All apps