Retrospective Facilitation Guide (Sprint Retro)

A structured protocol for team retrospectives — periodic meetings to reflect on process and continuously improve. Pre-meeting: Set the stage with a clear time boundary (60-90 min) and the Prime Directive: 'Regardless of what we discover, we understand that everyone did the best job they could, given what they knew at the time.' The protocol: (1) Gather data (15 min): Each person silently writes sticky notes for three categories: What went well? What didn't go well? What should we try? (2) Group and theme (10 min): Cluster similar notes together, name each cluster. (3) Vote (5 min): Each person gets 3 dots to place on the themes they most want to discuss. (4) Discuss top themes (30-40 min): For each top-voted theme, explore what happened and why. (5) Action items (10 min): Convert insights into 1-3 specific, owned, time-bound action items. Rule: never more than 3 action items — completion rate drops dramatically above this number. (6) Follow up: Start the next retrospective by reviewing last retro's action items.

When to use it

At the end of every sprint, project phase, or significant work period (typically every 2-4 weeks). After project completions or major milestones. After incidents or failures. After organizational changes. The cadence matters more than the timing — regular retros build trust and a culture of continuous improvement.

How it can help

Creates the only reliable organizational learning loop that actually works at team level. Most teams repeat the same mistakes because they never pause to reflect systematically. The retrospective protocol provides that pause with enough structure to produce actionable outcomes rather than vague complaints. The 3-action-item limit is critical — it prevents the 'improvement theater' of listing 15 changes and completing none. Teams that run retros consistently for 6+ months show measurable improvement in velocity and satisfaction.