mediumScenarioBehaviouralMidSeniorLead
How do you run a retrospective that actually changes something, and what do you do when the team has stopped engaging with them?
5 min readUpdated 2026-08-15
Answer
Short answer
A retrospective changes something when it ends with one owned improvement that enters the next Sprint Backlog as work. Disengagement is nearly always evidence that previous actions went nowhere, so the fix is to close the loop on old commitments before redesigning the format.
The facilitation test is whether the retrospective produces a decision the team can actually act on. Good facilitation narrows a broad complaint into one experiment, one owner, and one follow-up point. Weak facilitation collects feelings and actions without changing the next sprint.
Was this answer helpful?
Likely follow-ups
- The same issue comes up in four consecutive retros. What does that tell you and what do you do?
- A manager attends and the team goes quiet. How do you handle it, during and afterwards?
- How would you retrospect with a team split across two time zones and a language barrier?
- Your team asks to drop retros entirely because they are a waste of time. What is your answer?
Related questions
- Your Product Owner says everything in the sprint is top priority and refuses to rank the backlog. How do you handle it?mediumAlso on facilitation and scrum-master4 min
- The team has missed its Sprint Goal four sprints in a row. What do you do as Scrum Master?mediumAlso on retrospective and scrum-master6 min
- The engineering manager runs your team's Sprint Planning and assigns every item to a named person up front. The team says it works fine. What do you do?hardAlso on scrum-master6 min
- A team tells you the scaled agile rollout is process for its own sake and wants no part of it. What do you do?hardAlso on facilitation7 min