Improving Software Quality with Retrospectives
summary
Four concrete retrospective exercises are explained with outcomes and how to run them: root cause analysis (dig multiple causes not just 5 whys, quantify lost hours and prioritize one or two problems, co‑facilitate and communicate actions), future perspective (design a perfect product then map back to current steps), self assessment game (gamified health checks plus testing and quality card packs), and stop the line (bell/rope ritual to surface and fix issues immediately). Slides and templates are available on SlideShare.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:35Digital scaling transformation
- 2:29HR retrospective
- 5:18Retrospective exercises
- 6:12Cross analysis
- 7:51Root cause analysis
- 9:07Cost benefit
- 13:38Future perspective
- 16:37Strengths
- 23:08Stop the line retrospective
- 26:06Bring it back to the team
- 27:06Bonus
related talks
43mImproving Software Quality with Retrospectives
38mRetrospectives Antipatterns Avoid my Mistakes
01h 43mProject Retrospectives (Why, How, When)
20mOptimizing Agile Practices: The Retrospective
32mRetrospectives
30mNoRetrospectives
48mImproving and Extending Retrospective Outcomes
56mESSENTIALS - Retrospectives: Shifting Towards Value