Agility ≠ Speed - Agile Development
summary
Argues that agility is not raw speed but the ability to change direction and respond, claiming teams optimize speed not velocity and often measure rate instead of velocity includes direction. Shows tooling pitfalls: story points morph into a currency, burndown vs burnup/cumulative flow misleads, and metrics drive wrong behavior. Gives concrete contrasts (100k vs 1M LOC teams — the smaller had tests, CI and went home on time), introduces technical neglect and says failure demand 80–90% of work is common.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:30Dictionary definition of agility
- 6:11Agility as observation
- 8:56Agility vs speed
- 13:32Agile development history
- 16:39Ease over speed
- 21:32Measuring progress
- 27:55Story points pitfalls
- 32:09Business value limits
- 40:41Predicting the future
- 46:20Agility and incomplete knowledge
- 50:15Agile Manifesto deeper
- 55:50Value vs failure demand
- 1:03:14Technical debt root cause
- 1:12:41Copying practices blindly
- 1:17:21Group intelligence
- 1:23:17Processes and tools overemphasis
- 1:26:23Acceleration not speed
- 1:28:47Slowing down to see
