L
LEARNING
Agile vs Waterfall approaches: continuous cycle vs linear sequence
Requirements
De
n
v
Design
Implementation
Verification
Requirements
Track & Monitor
Maintenance
AGILE
• Continuous cycles
• Small, high-functioning,
collaborative teams
• Multiple methodologies
• Flexible/continuous
evolution
• Customer involvement
WATERFALL
• Sequential/linear stages • Best for simple,
unchanging projects
• Upfront planning and
in-depth
• Close project manager
documentation
involvement
• Contract negotiation
Agile vs Waterfall: when to use
AGILE WATERFALL
Style and culture Collaborative, iterative, flexible Disciplined, linear, structured
Project scope Unclear in advance; likely to change Well-defined; constrained by contract terms
and/or regulation and compliance
Team structure Small, cross-functional and flexible Larger, functional with defined roles
Customers Expectation of regular engagement Limited involvement at key milestones only
Documentation
requirements Minimal Upfront and in-depth
Testing Frequent and iterative Pre-defined and limited
Nature of
project/product New/greenfield with minimal
dependencies; multiple deliverables Enhancement to legacy products/projects
with dependencies; fully completed project
at project end
Timeline and
deadlines Short, flexible; final deadlines hard to set Fixed and firm; final deadlines clear and set
Budget Some flexibility for iteration Fixed and inflexible
Management Relies on close and collaborative
working relationships More predictable; tried and tested; can be
easier to manage
76 // Future Talent