Sprint Retrospective
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
The sprint retrospective is a review meeting held at the end of every sprint in which the whole team discusses three questions: what went well, what needs improvement, and how to do better next time. It builds continuous improvement into the rhythm of work, so the team learns and adjusts every sprint instead of only summarizing when a project ends or fails.
SCAFFOLDING EFFECT
Reduce cognitive load
- Name it to fix it: collect what went well, what to improve, and concrete actions in three columns - Keep it actionable: pick one to three improvements the team can actually ship next sprint - Verify the loop: check in the next sprint whether last sprint's improvement worked
Anchor fast decisions
Because the review arrives every sprint instead of at project end, learning is paced into the work rhythm and improvement compounds rather than arriving too late to help. Short cycles of reflection feed cumulative process change, so each adjustment is small enough to ship and each following sprint tests whether it held.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Scrum_(project_managementverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS