...
| Waterfall | Scrum | |
|---|---|---|
| Fundamental Assumptions | Systems are fully specifiable, predictable, and can be build through meticulous and extensive planning. | High-quality, adaptive software can be developed by small teams using principles of continuous design improvement and testing based on rapid feedback and change. |
| Control | Predictive: decisions are based on forecasts | Empirical: decisions are based on realities you observe in the actual project |
| Management Style | Command-and-control (amber organizations) | Leadership-and-collaboration (orange and green organizations) |
| Knowledge Management | Explicit | Tacit |
| Role Assignment | Individual - favors specialization | Self-organizing teams - encourages role interchangeability |
| Communication | Formal and documented | Frequent and facilitated |
| Customer's Role | Important | Critical |
| Organization of Work | Guided by architectural level and tasks (vertical slices by architectural level) | Guided by product features (horizontal slices through each architectural layer) |
| Development Model | Life cycle model | Evolutionary/Incremental delivery model |
| Desired Organizational Structure | Mechanistic (bureaucratic with high formalization) | Organic (flexible and participative, encouraging interpersonal interactions) |
...