Facilitation tips for scrum masters
The difference between a retro people endure and a retro people look forward to isn't the tool — it's ten small facilitation habits. These are the ones senior coaches use without thinking.
Updated
Set the tone in the first 60 seconds
Open with the prime directive: 'We assume everyone did the best they could with what they knew at the time.' It sounds hokey until you watch it disarm a tense room.
Manage the dominant voice without shaming
Use a round-robin or stacked-speaker order so everyone contributes once before anyone contributes twice. If one person still dominates, name the dynamic privately after the meeting — never in front of the team.
Surface dissent deliberately
Ask: 'What's the version of this we're not saying out loud?' or 'Who disagrees with the room?'. Most teams default to harmony — your job is to make disagreement safe.
Time-box ruthlessly
Five minutes for ideation. Ten for grouping. Fifteen for discussion. When the timer ends, end the topic. Open-ended retros punish the people who want to leave on time.
Use silence as a tool
After asking a hard question, count to ten silently before rescuing the room. The first answer is rarely the most honest one.
Limit yourself to three actions
Teams cannot meaningfully change six things at once. Pick the top three by vote, name an owner, set a due date, and abandon the rest with no guilt. Better to do three than to list twelve.
Always check the previous retro's actions first
Five minutes at the start, every time. If actions consistently aren't done, the problem is the process — not the people. Smaller actions, clearer owners, or a different cadence.
End with one round of appreciation
A single sentence each — what someone else did this sprint that you appreciated. Costs two minutes. Pays back tenfold in team cohesion.
Vary the format every 3–4 sprints
Same format = same answers. Rotating between Start/Stop/Continue, Sailboat, 4Ls and Lean Coffee keeps the team thinking from different angles.
Retros are not status meetings
If your retro keeps drifting into demo or planning, your demo or planning is broken. Fix the upstream meeting rather than letting the retro absorb it.
Habits are portable; tools make them cheaper
None of these ten habits depend on a particular product — a shared doc and a countdown timer can carry most of them. But the right tool removes the friction that makes good habits lapse under time pressure. The “always check last retro’s actions first” habit is trivial when a tool carries actions forward automatically; it quietly dies when someone has to dig through old boards. A guided, phase-driven flow like Retrium enforces time-boxing for you, while TeamRetro and Parabol keep owners, due dates and carry-over attached to each action so the discipline survives the week. If you are still choosing, the tool directory lets you filter by the facilitation features these habits lean on.
Where to go next
Habit nine is “vary the format” — our twelve retrospective formats guide gives you the rotation. Habits six and seven are about the afterlife of a retro, which is the whole subject of why your action items never get done. And if you facilitate the other scrum events too, the scrum master facilitation guide applies the same time-boxing discipline to planning, review and refinement.