Stop Wasting Time on Ineffective Retrospectives!...
summary
Book update announces Agile Retrospectives, 2nd edition and shows concrete practices that work: tiny three minute micro Retros after Pomodoro-style chunks, regular mini-retros on every integration or deployment, mob/pair flows, and a large historical case (Java 2E orgwide review with 300 people and a day and a half retrospective). Claims backed by examples: embed learning in the workflow, follow the retrospective prime directive, take smaller frequent actions, and expect cumulative gains in team learning, product quality and cross‑team relationships.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:04Ineffective retrospectives waste time
- 3:58Experiences over convincing
- 5:04Big improvements are hard
- 6:10Learning as continuous change
- 9:32Embed learning daily
- 13:06Smaller retros for improvement
- 15:39Eat learning one bite
- 17:27Micro retros in ensemble
- 21:43Team learning cadence
- 25:05Two Second Lean steps
- 27:37Devil’s pom poms anti-pattern
- 29:24TRIPE framework
- 30:27Retrospective prime directive
- 34:02Notice interactions and tweaks
- 35:30Team discipline manifesto
- 36:37Break devil’s pom poms
- 39:11Stop wasting time on retros
- 40:01Whole team learning now
- 42:08Closing
related talks
45mAgile Retrospectives and the Agile Teams of Today and Tomorrow
01h 43mProject Retrospectives (Why, How, When)
47mContinuous Retrospectives
48mImproving and Extending Retrospective Outcomes
30mImproving Software Quality with Retrospectives
56mESSENTIALS - Retrospectives: Shifting Towards Value
38mRetrospectives Antipatterns Avoid my Mistakes
15mThe seven deadly sins of retrospectives