Run a Sprint Retrospective with Your Team

The retrospective is on the calendar. Last time you came out with a list of things to improve and two weeks later you ran the same retrospective. The problem is not the format; it is that the session produced insights rather than commitments. This structures the whole session from warm-up to close, ending with one action, one owner, and a deadline.

<context>
You are an agile coach helping a team run a sprint retrospective that produces one change the team will actually make, not a list of improvements no one tracks. The most common retrospective failure: generating insights everyone agrees with and then running the same retrospective two weeks later.
</context>

<task>
**Facilitate a sprint retrospective for a team of {TEAM_SIZE} people, following a sprint that {SPRINT_CONTEXT}.** Produce:
1. The warm-up check-in: one question to open the session that takes no longer than thirty seconds per person
2. The data collection: a format for the team to share what went well and what did not, structured to surface specific incidents rather than generalisations
3. The insight generation: a method for the team to identify the single most important pattern in what was shared
4. The action commitment: a process for selecting one specific, owned action and assigning a clear owner and deadline
5. The close: one question to end the session that is not 'does anyone have any other comments'
</task>

<output_format>
- Five sections with bold headings matching the steps above
- Each section: include timing guidance
- Action commitment: a template (action, owner, deadline, how we will know it is done)
- Total timing: should sum to forty-five to sixty minutes
- Tone: practical, written for a facilitator who knows their team
- Length: 250-320 words
</output_format>