A Repeatable Retrospective Flow for Agile Coaches

The facilitation challenge

Agile coaches need enough consistency to compare facilitation outcomes without imposing identical diagnoses on teams with different maturity, context, and trust.

What a good session should produce

• A repeatable room flow across teams
• Adjustable 20–60 minute pacing
• Team-specific history and mission follow-up
• Identity-hidden issue and solution authorship in the room
• Clear separation between facilitator guidance and team decisions

A practical workflow

1. Choose a coaching intention. Decide whether the session should surface risk, improve flow, or strengthen follow-through.
2. Keep the mechanics stable. Use the same private-write, reveal, discuss, and decide rhythm so the team can focus on content.
3. Observe participation. Notice completion and voting patterns without trying to identify anonymous authors.
4. Coach the experiment. Challenge oversized actions until the team can test one change within a sprint.
5. Review evidence. Start the next session with mission status and what the team learned.

Suggested agenda

• 5 min previous mission and mood
• 10 min signals
• 5 min impact ranking
• 15 min action design and discussion
• 5 min vote, owner, and review date

Common failure modes

• Comparing team mood scores as performance rankings
• Turning anonymity into an investigation
• Choosing the action for the team
• Changing the format so often that teams never learn the rhythm

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.