What is Agile vs Waterfall?
Waterfall is a sequential project methodology — requirements, design, build, test, deploy — where each phase completes before the next begins. It works for projects with stable requirements (construction, manufacturing, regulated software). Agile is an iterative methodology — short cycles (sprints) of plan-build-test-review — that delivers working increments and adapts based on feedback. The Agile Manifesto (2001) prioritized individuals, working software, customer collaboration, and responding to change over process, documentation, contracts, and plans. Agile dominates modern software development; Waterfall remains appropriate for regulated, contractual, or physical-deliverable projects. Many organizations use hybrids — Waterfall for governance and milestones, Agile for delivery within phases.
How Agile vs Waterfall actually works
The framework breaks down into the following moving parts. Knowing what each piece is — and what it is not — is what separates a B-grade answer from an A-grade answer in a written assignment.
- Waterfall — sequential, plan-driven, stable requirements
- Agile — iterative, adaptive, change-tolerant
- Agile sprints typically 1-4 weeks
- Each appropriate to different project types
- Many organizations use hybrid
A worked example: Spotify (agile) vs SpaceX (mostly waterfall)
Spotify is a textbook agile organization — small autonomous squads, two-week sprints, continuous deployment, willingness to change direction. The methodology fits software development with fast feedback loops and acceptable cost of failure. SpaceX, by contrast, follows mostly waterfall for rocket development — extensive design and review before building, sequential testing, no "minimum viable rocket" iteration. The methodology fits hardware where failure costs are catastrophic. Both companies are operationally excellent; both choose the methodology that matches their problem type. Forcing agile on SpaceX or waterfall on Spotify would degrade both.
Don't lose marks for these
- Defaulting to one methodology
- Pure agile on regulated/contracted projects
- Pure waterfall on adaptive software projects
How to use this on the exam
Score-maximizing moves
- Compare both methodologies
- Match to problem type
- Cite hybrid as common
When to use Agile vs Waterfall (and when not to)
Use Agile vs Waterfall when your assignment asks you to analyze, structure, or recommend — and when you have at least two data points to populate every cell of the framework. Skip it when the question is asking for a numerical answer or a single recommendation, since Agile vs Waterfall is a structuring tool, not a calculator.