Grace Williams·
Picked the Sailboat format and got a minute-by-minute retro plan with anonymous survey questions
Designs engaging retrospective formats with activities, discussion prompts, and actionable improvement commitments.
Sprint Retrospective Facilitator
You are an Agile team facilitator who designs transformative retrospectives. Design a Sprint {{sprint_number}} retrospective for {{team_name}}, a team of {{team_size}} people working on {{project_name}}. Sprint duration was {{sprint_duration}} and they completed {{completion_rate}}% of committed story points. Key events this sprint: {{sprint_events}}. The team mood is: {{team_mood}}. Create: (1) A retrospective format selection with rationale (e.g., Start-Stop-Continue, 4Ls, Sailboat, Speed Car), (2) A detailed facilitation guide with time-boxed activities for a {{retro_duration}} session, (3) Pre-retro survey questions to gather input anonymously, (4) Icebreaker activity tailored to the team, (5) Main activity with step-by-step facilitation instructions, (6) Discussion prompts for uncovering root causes, (7) Prioritization method for improvement items, (8) A commitment template for 2-3 actionable improvements with owners and due dates, (9) A team appreciation/shout-out segment, (10) Closing activity to end on a positive note, (11) Follow-up plan for tracking improvement commitments. Make it psychologically safe and energizing.
Ergebnisse
# Sprint 14 Retrospective — Team Falcon (6 people, "Checkout v2")
Sprint: 2 weeks, completed **68%** of committed points. Key events: a prod incident mid-sprint, a late scope change. Mood: tired but not demoralized.
## Format choice
**Sailboat** — fits a sprint where external forces (the incident, scope change) dominated. Wind = what pushed us, anchors = what held us back.
## Facilitation guide (60 min)
| Activity | Min |
|----------|-----|
| Pre-retro survey review | 5 |
| Icebreaker: one-word mood | 5 |
| Sailboat brainstorm (silent) | 15 |
| Group + discuss themes | 15 |
| Root-cause on top 2 | 10 |
| Vote + commit to actions | 8 |
| Appreciations + close | 2 |
## Pre-retro survey (anonymous)
- What slowed us most this sprint?
- What should we keep doing?
- Energy level 1–5?
## Discussion prompts
"What made the incident take so long to resolve?" / "Why did the scope change land so late?"
## Commitments (template)
| Action | Owner | Due |
|--------|-------|-----|
| Add a runbook for the failed service | Priya | Sprint 15 |
| Scope-change cutoff at day 3 | PM | Immediate |
**Appreciations:** each person shouts out one teammate. **Closing:** "One thing you're looking forward to next sprint." **Follow-up:** review action items at the next retro's start — no orphaned commitments.
Modell: Claude Sonnet 4
19 Likes5 SavesScore: 13
2 Kommentare
Sofia Almeida·
The contingency column is what makes the plan actually hold up.
Ethan Reed·
Best project management template I've found on here.