The question "agile or waterfall?" is really a question about uncertainty and the cost of change. When you know what to build and changing course is expensive, plan carefully and execute (Waterfall). When you are discovering what to build and change is cheap, deliver small and learn fast (Agile). Most organisations live in between — which is why hybrid is now the most common approach in practice.
Side-by-side comparison
| Waterfall | Agile | Hybrid | |
|---|---|---|---|
| Planning | Detailed, up front | Continuous, just-in-time | Milestones up front; details iterative |
| Scope | Fixed; changes via change control | Flexible; reprioritised each iteration | Fixed at milestone level, flexible within |
| Delivery | One release at the end | Frequent increments | Increments within phases |
| Customer involvement | At phase gates | Continuous | Regular reviews plus gates |
| Risk profile | Back-loaded (found in testing) | Front-loaded (found early) | Mixed |
| Documentation | Comprehensive | Just enough | As governance requires |
| Progress measure | Milestones, % complete, EVM | Working increments, velocity | Both |
| Contracts | Fixed price, fixed scope | Time and materials, capped | Fixed phases with flexible content |
| Typical tools | Gantt, CPM | Boards, backlogs | Gantt for milestones + boards for delivery |
Decision checklist
Score each statement 1 (disagree) to 5 (agree). A higher total favours agile:
- Requirements are likely to change or emerge as we learn.
- We can deliver something useful in a few weeks.
- A customer or product owner is available weekly.
- The team is small, stable and co-located or well connected.
- Mistakes are cheap to fix after release.
- Regulation does not require full design approval up front.
Roughly: 6–14 → Waterfall; 15–22 → Hybrid; 23–30 → Agile. For a more detailed recommendation, take our methodology quiz.
What hybrid looks like in practice
- Phase-gated agile: a plan with milestones for funding and governance; Scrum sprints inside the build phase.
- Agile software, waterfall hardware: common in IoT and manufacturing — hardware follows a fixed schedule, software iterates against it.
- Waterfall planning, Kanban execution: a fixed scope delivered through a flow-based board with WIP limits.
The key to hybrid is being explicit about which parts are fixed and which flex, and reporting each part with the right measures.
Myths to drop
- "Agile is faster." It delivers value sooner, but total time depends on scope.
- "Waterfall can't handle change." It can, through change control — it is just more expensive.
- "Agile means no documentation or deadlines." Agile teams have both; they just avoid unnecessary ones.
Put this into practice
Use our free tools to apply what you just read — or get a free consultation if you want an expert to look at your project.