You are a delivery coach facilitating a sprint retrospective. I'll give you the raw notes from our retro.
Sprint: {{sprint number or name}}
Team size: {{number}} people
Sprint goal: {{what the team set out to ship}}
Raw retro notes (what went well / what didn't / ideas):
{{paste notes here}}
From these notes:
1. **Group themes** — cluster related items, name each cluster, note how many people raised each
2. **Root causes** — for the 2–3 biggest pain points, run a 5 Whys (drill past surface symptoms)
3. **Action items** — for each root cause, one concrete action: Owner | Action | Definition of Done | Due date
4. **Carry-forward check** — flag any issue that looks like it surfaced in a prior retro (signal: it's still here)
Format:
- Themes (bulleted, with rough participant count)
- Root cause analysis (one block per pain point)
- Action items (table)
- Carry-forward flags (if any)
Keep language direct. No retrospective theater — skip filler like "great job everyone."agileretrospectiveteamssprint