Facilitating Sprint Retrospectives

For a 6-person team, 45-minute retro:

1. Day before: Share anonymous input doc with three columns (Start / Stop / Continue). Send reminder 2 hours before deadline.
2. First 5 min: Silently read/cluster submitted items into themes.
3. Next 25 min: Discuss top themes (aim for 3-5), one column at a time — Start, then Stop, then Continue.
4. Next 10 min: Convert discussion into concrete action items.
5. Last 5 min: Assign exactly one owner per action item, restate deadline expectations, close.

Progress:

• Send anonymous input doc 24 hours before retro
• Cluster submissions into themes before the meeting starts
• Timebox each column discussion (roughly 8 min Start, 8 min Stop, 8 min Continue)
• Convert top themes into 3-5 concrete action items
• Assign one named owner per action item
• Send recap notes within 24 hours with owners and due dates
• Carry forward unresolved action items to next retro's agenda

Step details

1. Pre-collection (day before meeting)

• Use a shared doc with three headers: Start / Stop / Continue.
• Keep it anonymous — no names next to entries, submissions can be freeform bullet points.
• Send one reminder if fewer than half the team has responded by mid-day.

2. Pre-meeting clustering (facilitator, 10-15 min before or first 5 min of meeting)

• Group similar entries together (e.g., three "standup is too long" comments become one theme).
• Rank themes by frequency/intensity, not just count — a strongly-worded single entry can outweigh three mild ones.
• Pick top 3-5 themes total across all three columns to fit the timebox. Don't try to discuss everything submitted.

3. Discussion (25 min, ~8 min per column)

• Go in order: Start → Stop → Continue. This order works because Start/Stop generate energy and concrete change, Continue reinforces morale before closing.
• For each theme, ask: "What would this look like in practice?" — push past venting into specifics.
• If a topic clearly needs more than the timebox allows, note it as "needs separate discussion" and move on. Don't let one theme eat the whole meeting.

4. Action item conversion (10 min)

• Every theme that survived discussion needs to become either an action item or an explicit "no action" decision — don't let things trail off ambiguously.
• Action items should be concrete and doable within one sprint (e.g., "Add 15-min buffer to sprint planning" not "improve planning").

5. Owner assignment (5 min, closing)

• One owner per action item — never split ownership. If it needs two people, one is still the accountable owner.
• Ask for volunteers first; assign directly if none in ~10 seconds.
• State the check-in point explicitly ("we'll check on this next retro" or "ping the channel when done").

6. Follow-up (within 24 hours)

• Send a short recap: themes discussed, action items, owners, due/check-in dates.
• Add unresolved/carried-over items to the top of next retro's input doc so they're visible.

Example 1: Input: Submissions include four "Stop" entries about too many context-switching interrupts during focus blocks, two "Start" entries about wanting a shared on-call runbook, and one "Continue" about keeping Friday demo time. Output:

• Theme 1 (Stop, highest frequency): Interrupt-driven context switching → Discuss → Action: "Set up two 2-hour no-meeting focus blocks per day in team calendar." Owner: Priya. Check-in: next retro.
• Theme 2 (Start): On-call runbook missing → Discuss → Action: "Draft runbook doc, share for review." Owner: Marcus. Due: end of next sprint.
• Theme 3 (Continue): Keep Friday demos → No action needed, note as affirmed practice.

Example 2: Input: A theme generates heated disagreement about whether code review turnaround time is actually a problem, eating 15 minutes with no resolution. Output: Facilitator interrupts at the 15-minute mark: "This clearly needs more than we can do here — let's take it offline as a 30-min follow-up with just the reviewers involved, and move on to close out today's actions." Logs it as a carry-over item for next retro's doc, not lost.