The Power of Retrospection
summary
Argues that regular, short retrospectives turn learning into measurable change, using a real-time timeline of color‑coded cards to capture events and emotions, enforce no naming no blaming, and derive small experiments as action items. Shows a concrete low‑cost case: a cardboard‑box standing experiment that proves standing boosts energy and leads to buying standing desks. Recommends running many tiny tests — one company averages six experiments per two‑week iteration — collect simple metrics, and post results for organizational learning.
AI-written summary · about
chapters (25)
- 0:00Retrospectives intro
- 1:34Agile retrospectives
- 5:09Agile manifesto reflection
- 8:07Thinking and reflection
- 11:27Small adjustments power
- 15:01Postmortems vs learning
- 20:49Experience vs learning
- 25:28First retrospective timeline
- 37:01Emotional weight of failures
- 41:19Learning not blame
- 45:34No naming no blaming rule
- 48:25When to run retrospectives
- 51:14Future improvements
- 55:31Problems into experiments
- 1:01:09Retrospectives as experiments
- 1:06:10Prioritizing action items
- 1:14:31Food break power
- 1:16:22Real-time timeline building
- 1:22:32Ground rules facilitation
- 1:26:33Timeline analysis patterns
- 1:30:11Long project exercises
- 1:32:00Running effective experiments
- 1:36:42Cheap experiments improvement
- 1:38:31Premortems future techniques
- 1:40:16Facilitation resources
related talks
47mContinuous Retrospectives
56mESSENTIALS - Retrospectives: Shifting Towards Value
45mAgile Retrospectives and the Agile Teams of Today and Tomorrow
48mImproving and Extending Retrospective Outcomes
09mA retro of retros: how Sprint retrospectives can be both fun and productive
38mRetrospectives Antipatterns Avoid my Mistakes
42mStop Wasting Time on Ineffective Retrospectives!...
30mImproving Software Quality with Retrospectives