Why do we need Scrum?
The problems with plan-everything-first delivery: late feedback, changing requirements and rising cost of change, and how many small bets fix them.
Transcript
The traditional way: plan everything up front, then build, test and deliver.
Months pass before anyone sees working software.
Meanwhile requirements change, and the customer only reacts at the very end.
The later we find a mistake, the more it costs to fix.
And software work is complex: we cannot predict everything in advance.
Scrum replaces one big bet with many small ones.
Build a little, show it, learn, and adjust.
Plan a little. Learn a lot.
More in this series
1:17Why Scrum is empirical
Why complex work needs steering by evidence, and how transparency, inspection and adaptation depend on each other.
1:04Why short sprints?
Why timeboxes create fast feedback, smaller risk and protected focus.
1:27Why Scrum roles and events exist
The problem each Scrum accountability and event solves.
1:51Scrum vs Kanban
What the two share, and how they differ in cadence, limits, change, roles and metrics, plus when to choose each.