Agile vs Waterfall

Agile vs. Waterfall poster.
Two different approaches, same goal.

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 / ApproachWaterfallAgile
FocusOn processesOn people
ManagementBy plansBy changes
Development StyleWaterfall/ Long iterationsIncremental, iterative short iterations
RequirementsPlanned at the beginningUpdated before every iteration
Customer involvedAt the beginning and the endAll the time
FeedbackMinimalFrequent
Social aspectsPlan and controlTrust, responsibility, motivation
Team organizationHierarchicalSelf-organized teams
LeadershipDirectingCoaching
Change managementMinimization of changesAccept and adapt to changes
DocumentationExhaustiveJust enough
CommunicationMainly writtenMainly personal
Product deliveryAs a whole at the endFrequent, but partial






The newest post: MVP Types