Agile Retrospectives and the Agile Teams of Today and Tomorrow
summary
Claims that retrospectives are mandatory under Agile Principle 12 and must produce continual team learning; offers concrete practices: short pomodoro 25‑minute micro‑retro cycles, daily end‑of‑day micro‑retros, and occasional surprise retrospectives after big events. Uses a five‑step framework — set the stage gather data generate insights decide what to do close — and insists on picking one experiment to run, assigning a small subgroup to implement it, and reporting results at the next retro so improvement becomes ongoing work.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:14Retrospectives matter
- 6:44Retrospective definition
- 15:21Continuous improvement
- 20:21Psychological safety
- 23:35Agile fluency
- 33:54Effective practices
- 40:36Resistance to participation
- 41:40Agile adoption barriers
- 44:40Q&A
related talks
20mOptimizing Agile Practices: The Retrospective
42mStop Wasting Time on Ineffective Retrospectives!...
01h 43mProject Retrospectives (Why, How, When)
08mHow to turn an agile retrospective into teambuilding
30mNoRetrospectives
48mImproving and Extending Retrospective Outcomes
47mContinuous Retrospectives
20mLearn to Facilitate 5 Minutes of Mindfulness in Retrospectives