Online Retrospective Game for Scrum Masters

The facilitation challenge

Scrum Masters must protect the process without becoming the source of every idea or the owner of every improvement. In a vocal group, the first explanation can anchor everyone else; in a quiet group, collecting useful input can consume the entire meeting.

What a good session should produce

• Equal private input before discussion
• A visible timebox and one facilitation control at a time
• Team-led prioritisation and private voting
• A mission with an owner and target date
• A previous-mission review at the next retro

A practical workflow

1. Prepare the boundary. Choose the sprint and time budget, then share the participant link before the meeting.
2. Collect before interpreting. Let everyone submit privately. The host sees completion progress, not authors.
3. Focus one Boss. Use team reactions to select the highest-impact issue instead of facilitator preference.
4. Separate ideas from debate. Collect one action per player before opening the discussion.
5. Close accountability. Assign the selected mission and review it first next time.

Suggested agenda

• 3 min mood check
• 7 min issue collection
• 5 min prioritisation
• 5 min solution writing
• 8 min discussion and vote
• 2 min ownership

Common failure modes

• Explaining anonymous entries on behalf of contributors
• Treating the top vote as automatic truth
• Allowing discussion before everyone proposes an option
• Accepting an action without an owner

Where RetroRally fits

Boss Battle is the format currently playable in RetroRally. It combines an anonymous-to-the-room mood check and issue collection with impact ranking, one concrete solution per player, discussion, private voting, and an owned mission. See every stage or try the live room.

Continue learning

Browse questions by team situation, compare facilitation templates, or use the complete sprint retrospective agenda.