MidScenarioTeam facilitation
The team's retrospectives feel stale. What do you change?
Try answering first
Model answer
First I find out why they feel stale. Common causes are the same format every time, no follow-through on actions, low psychological safety, or a lack of data.
What I would change:
- Vary the format. Try different structures, such as Start/Stop/Continue, 4Ls, a timeline of the Sprint, or a sailboat exercise. Change the setting or the facilitator now and then.
- Bring data. Show metrics such as cycle time, escaped defects and mood over time, so talk is grounded in facts.
- Follow through. Limit to one to three improvements, give each an owner, and review them at the start of the next retrospective. A team that sees change happen keeps engaging.
- Build safety. Make sure people can speak honestly, with anonymous input if needed, and that the event is not used to assign blame.
- Zoom out or in. Sometimes focus on one theme, such as collaboration or quality, rather than everything.
I also ask the team directly how to make the retrospective more useful.
Key points
- Diagnose the cause before changing the format
- Vary formats and bring data to the discussion
- Pick a few actions with owners and review them next time
- Protect psychological safety
Likely follow-ups
- What would you do if the same issue keeps coming up and nothing changes?
- How do you run a retrospective after a failed release?
Common mistakes
- Collecting many action items and completing none
- Running the same format every Sprint without checking if it works