The 4 Endings of a Retrospective
summary
A practical framework maps four retrospective endings—bitter, bittersweet, semieet, sweet—to whether a team achieves its external wants and internal needs, and gives concrete signals to watch (overconfidence, stakeholder pressure, technical debt, personal sacrifice, clarity of vision, mentoring). Actions include track endings per sprint as a quick metric, raise transparency on hidden needs, run themed role-play retros for quieter voices, and prioritize needs before wants. The goal is more sweet endings; the talk shows which behaviors to amplify or correct and how to run retros that actually change outcomes.
AI-written summary · about
chapters (13)
- 0:00Retrospective frameworks
- 1:07Protagonists' wants vs needs
- 3:17Four story endings
- 6:02Story endings in retrospectives
- 9:57Bitter retrospective signs
- 12:45Bittersweet retrospective signs
- 15:17Semi-sweet retrospective signs
- 17:43Sweet retrospective signs
- 20:53Mapping team signals to endings
- 21:35Creating sweet endings
- 23:43Cinema techniques for retrospectives
- 25:51Endings in sprints
- 27:15Q&A
