Why Scrum Is So Often 'Failed' and Criticised
summary
The talk explains why Scrum appears to fail when organizations keep fixed-time/fixed-budget constraints, maintain traditional hierarchies and isolated teams, or follow Scrum rituals without real change. It argues that real enablers are CI/CD and automated tests, stable cross-functional teams, and managers acting as enablers, and notes a concrete metric: one story point often corresponds to about $2–3k of team cost; with those practices iterative delivery works, otherwise Scrum mainly just exposes problems.
AI-written summary · about
chapters (8)
- 0:00Scrum criticised
- 6:45Hierarchy’s impact
- 12:22Project management issues
- 18:03Checkbox Scrum
- 23:14Code quality in Scrum
- 28:12Manager’s role
- 33:09Scrum values
- 37:48Scrum as change tool
