Waterfall Model
Waterfall is the sequential delivery model — requirements, design, build, test, deploy, each phase completing before the next starts — still the right fit where requirements are stable, compliance gates are real, and late change is genuinely expensive.
When sequential still wins
Waterfall’s reputation suffers from misuse, not from the model itself: it fits projects where the problem is well understood, specifications must be signed off before build (public tenders, regulatory submissions), or hardware/certification gates make iteration cost-prohibitive. The real failure mode is pretending requirements are stable when they are not.
Most regulated delivery is hybrid: waterfall-shaped governance around agile-shaped build — fixed scope and stage gates at the contract level, iterative sprints inside. Our agile-vs-waterfall guide covers where each model and the hybrid actually fit.
Related Standards
- •ISO/IEC/IEEE 12207 — software lifecycle processes
Further Reading
Need help with this?
We consult and build across all of these domains — tell us what you are working on.
