Agility ≠ Speed
summary
Argues that agility is responsiveness not raw speed, showing how metrics mislead: 1,000,000 vs 100,000 lines of code reveals which team wrote tests, refactored and reduced defects while delivery rates rise; story points become currency when teams convert points to time and end up measuring busyness, not value. Warns that velocity needs direction (a vector), that chasing throughput inflates technical debt, and that true agility is the ability to slow, change direction and experiment.
AI-written summary · about
chapters (14)
- 0:00Introduction by host
- 1:22Agility versus speed
- 3:05Agile as philosophy not process
- 8:04Productivity metaphor origins
- 10:53Measuring lines of code pitfalls
- 13:42Code base agility and responsiveness
- 16:54Story points and estimation issues
- 21:47Estimates as negotiation
- 24:37Dimensional analysis of metrics
- 27:27Velocity obsession dangers
- 28:55Goodhart’s law in metrics
- 30:39Velocity as vector quantity
- 32:22Busyness vs true agility
- 33:27Agility as acceleration
