Same project, two ways to build it. Watch both teams start — then change the requirements mid-way and see what happens.
| Question | Waterfall | Agile |
|---|---|---|
| When do stakeholders see working software? | Only at the end | After every sprint (every 2–3 weeks) |
| Requirements change mid-way — what now? | Hard to adapt; may scrap work | Next sprint's plan just includes the change |
| Feedback loops | One big one at the end | Many small ones, sprint after sprint |
| Risk | High — you find out late | Lower — problems surface fast |
| Best when | Requirements are truly fixed (rare) | Requirements evolve (most projects) |
Tip: press Start, then press Requirements change! mid-way through. Watch how each approach reacts — the waterfall team has a problem; the agile team adjusts next sprint.