Retrospective Template

A sprint retrospective template using the simplest format that works: what went well, what didn't, and what the team will try next. Add the action items with owners and review last retro's items first, so retros lead to change instead of repeating.

Download Word (.docx)Download Markdown (.md)

Free to use and adapt, no signup. The .docx opens in Word, Pages and Google Docs (File → Open → Upload).

The template

Sprint Retrospective

Team: [Team] Sprint: [Sprint / dates] Facilitator: [Name]

Attendees: [Names]

Last retro's action items

  • [Action] — [Owner] — [Done / Not done / Helped?]

What went well

  • [Point]
  • [Point]

What didn't go well

  • [Point]
  • [Point]

What we'll try next

  • [Experiment or change]

Action items

  • [Action] — [Owner] — [By when]
  • [Action] — [Owner] — [By when]

Or skip the template: upload the recording to the minutes generator

Wave AI's free meeting minutes generator transcribes the recording with speaker labels and fills in this structure for you: attendees, discussion, decisions and action items with owners. You can also paste a transcript from Zoom, Teams or Google Meet. No account needed.

Open the meeting minutes generator

When to use it

  • End-of-sprint retrospectives for scrum and agile teams
  • Project post-mortems and launch reviews
  • Quarterly team health check-ins
  • Any team that wants to improve how it works, not just what it ships

How to fill it in

  1. Review last retro's action items. Start by checking what the team said it would try. Did it happen, and did it help?
  2. Collect points silently first. Give everyone a few minutes to add their own points to each column before discussing.
  3. Group and discuss. Cluster similar points, talk about the biggest ones and keep the tone blameless: describe what happened, not who failed.
  4. Pick one to three changes. Turn the most important points into experiments with an owner, and review them at the next retro.

Notion-friendly Markdown

Paste this into a Notion page and the headings, lists, checkboxes and tables become Notion blocks. It also works in Obsidian, GitHub, Confluence and any Markdown editor.

# Sprint Retrospective

**Team:** [Team]   **Sprint:** [Sprint / dates]   **Facilitator:** [Name]

**Attendees:** [Names]

## Last retro's action items

- [ ] [Action] — [Owner] — [Done / Not done / Helped?]

## What went well

- [Point]
- [Point]

## What didn't go well

- [Point]
- [Point]

## What we'll try next

- [Experiment or change]

## Action items

- [ ] [Action] — [Owner] — [By when]
- [ ] [Action] — [Owner] — [By when]

Common questions

What are the three retrospective questions?

What went well, what didn't go well, and what will we try next? Some teams use Start / Stop / Continue or Mad / Sad / Glad instead; the headings change but the idea is the same. This template uses the three-question format.

How do you run a good retrospective?

Review last retro's actions first, let people add points silently before discussing, keep it blameless, and leave with one to three concrete changes that each have an owner. More than three rarely happen.

How long should a sprint retrospective take?

About 45 minutes for a two-week sprint is common, scaling up for longer sprints or post-mortems on big launches.

Can I get retro notes from a recording?

Yes. Upload the retro recording to Wave's free meeting minutes generator and choose "Retrospective": it groups what went well, what didn't and what the team will try next, written blamelessly, with action items.

Wave app screenshot showing meeting transcription
Wave AI note taker background pattern