“Keep it simple!” Retrospecting on retrospectives
summary
Claims that swapping fancy exercises for a short, metric-driven routine frees time and fixes real impediments. Uses flow metrics (lead time ~60 days revealed untestable tiny tasks; work item age 20 days exposed a silo) plus an always-open topics board and a weekly mob code‑review hour. Runs retros as: review ongoing actions, review metrics, discuss linked topics, record experiments. Prep time drops from hours to ~3–5 minutes, throughput stabilises at 3–4 items/week, teams run retros independently since Oct 2022. KISS throughput
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:47Retrospective mistakes
- 5:20Impressing with exercises
- 7:27Participant confusion
- 10:55Positive outcomes
- 13:01KISS principle
- 14:46Data for improvement
- 17:34Flow metrics
- 23:16KISS framework
- 24:42Lessons learned
- 26:32Call to action
related talks
47mContinuous Retrospectives
39mScaled Retrospective – improvements bigger than a Scrum Team
09mA retro of retros: how Sprint retrospectives can be both fun and productive
48mImproving and Extending Retrospective Outcomes
42mStop Wasting Time on Ineffective Retrospectives!...
44mStop wasting your time with Retrospectives
45mAgile Retrospectives and the Agile Teams of Today and Tomorrow
24mAgile working in a slow-moving world