Agile vs Waterfall

The main difference between Waterfall and Agile can be illustrated with the following triple constraints which can provide a rough overview. The rest of the differences that can provide a better overview can be found in the following table.

Agile vs. Waterfall Triple Constraints
Agile vs Waterfall triple constraints.

Aspect / Approach Waterfall Agile
Focus On processes On people
Management By plans By changes
Development Style Waterfall/ Long iterations Incremental, iterative short iterations
Requirements Planned at the beginning Updated before every iteration
Customer involved At the beginning and the end All the time
Feedback Minimal Frequent
Social aspects Plan and control Trust, responsibility, motivation
Team organization Hierarchical Self-organized teams
Leadership Directing Coaching
Change management Minimization of changes Accept and adapt to changes
Documentation Exhaustive Just enough
Communication Mainly written Mainly personal
Product delivery As a whole at the end Frequent, but partial


Similar posters

Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.
Little's law
Little's law Little’s Law is a theorem for queuing systems. It determines the average number of items in a stationary queuing system
User Story Creation
User Story Creation Creating a User Story is a continuous process based on the 3Cs phases, supported by INVEST, 5Ws, and the Definition of Done.
Radical Candor
Radical Candor Radical Candor is a framework describing four different behaviors. In order to become Radically Candid you need to understand all four types.
GSD / Get Stuff Done Whee
GSD / Get Stuff Done Whee Get Stuff Done Wheel is a framework for aligning and guiding the work of a team. It allows teams to deliver remarkable results more quickly
AIDA Model
AIDA Model The AIDA model is a model, where a persona moves through a series of steps to make a purchase decision, used in marketing, sales, planning...