MinutesMaster
Sign inStart free
Sprint retrospective template

Retrospective notes that end in actions someone owns

A blameless format for sprint retros, project post-mortems and lessons-learned sessions: what went well, what didn’t, the ideas for doing better — and the improvement actions with an owner each.

Start freeSee the example

5 free credits (2.5 hours of audio) · No credit card · No AI training on your data

When to use the retrospective template

Use it at the end of a sprint, a release, a project or an incident: any meeting where a team looks back to work better next time. Retros fail when the same problems come up sprint after sprint, so the notes need to show what the team decided to change and who is making it happen.

The template has three sections. What went well keeps the practices worth repeating. What didn’t go well records problems as facts about the work, not about people. Ideas for improvement collects the proposals; the ones the team commits to become action items with owners.

MinutesMaster writes this template in blameless wording: “the staging data was outdated”, not “someone forgot to update it”. The improvement actions land in the action items, and Follow-ups lists every open action across all your meetings — so next sprint’s retro can start by checking them.

At a glance
Built-in template in MinutesMaster
Retrospective
Group
Everyday
Default length
Standard
Sections of this template
  • What went well
  • What didn't go well
  • Ideas for improvement

Every template also writes the standard fields: overview, summary, participants, agenda, decisions, action items and the next meeting.

Structure

The structure of retrospective notes

The three classic retrospective questions, on top of the fields every set of minutes has.

Sections this template adds

  1. 1

    What went well

    List

    Practices, results and habits worth keeping, as the team named them.

  2. 2

    What didn't go well

    List

    Problems and frustrations, described as facts about the work rather than about people.

  3. 3

    Ideas for improvement

    List

    Proposals for doing it better next time; the agreed ones also appear as action items with owners.

In every set of minutes

Whichever template you pick, MinutesMaster also writes these fields:

  • Overview — one to three sentences on what the meeting was about and what came out of it.
  • Summary — the discussion condensed into a short read for people who weren’t there.
  • Participants — every speaker, with their name and role when it was said in the meeting.
  • Agenda — the topics actually discussed, in order.
  • Decisions — only what was explicitly agreed or adopted, kept apart from proposals and opinions.
  • Action items — tasks with an owner, and a due date when one was stated.
  • Next meeting — date, time and agenda points, if they came up.
  • Detailed minutes — a narrative record in paragraphs, with the times of the important moments.
Example

Example: sprint retrospective notes, filled in

A 45-minute retro of an invented checkout team after a two-week sprint, written up with this template.

RetrospectiveMicrosoft Teams bot · 45 min · English

Sprint 14 retrospective — checkout team

The payment provider migration shipped on time, but two hotfixes followed because staging data differed from production. The team agreed to refresh staging weekly, split large stories before planning and try a daily review rotation.

Summary

Sara opened by checking last retro’s actions: two of three were done. The team was pleased that the payment provider migration went live on schedule and that pairing helped on the hardest tickets. Two hotfixes were needed after the release because staging data no longer matched production. The refund flow, estimated at 8 points, took roughly three times as long as planned, and pull requests waited more than a day for review on average. The team chose three improvements and will try the review rotation for two sprints before deciding whether to keep it.

Participants

  • Sara Lindqvist — scrum master, facilitates
  • Tomás Ruiz — developer
  • Mei Chen — developer
  • Jonah Adler — developer
  • Fatima Zahra — QA

Agenda

  1. Actions from the last retrospective
  2. What went well
  3. What didn’t go well
  4. Improvements for sprint 15

Decisions

  • Try a daily review rotation for two sprints, then decide whether to keep it.
  • Stories estimated above 5 points are split before sprint planning.

Action items

OwnerTaskDue
Mei ChenScript a weekly refresh of staging data from anonymised production dataBefore the end of sprint 15
Jonah AdlerSet up the daily review rotation in the team calendarMonday
Sara LindqvistAdd “split stories over 5 points” to the planning checklist—

What went well

  • The payment provider migration went live on schedule.
  • Pairing on the two hardest tickets saved time and spread knowledge.
  • Dropping the Thursday sync freed up an hour a week without anyone missing information.

What didn't go well

  • Two hotfixes after the release: staging data no longer matched production.
  • The refund flow was estimated at 8 points and took about three times as long.
  • Pull requests waited more than a day for review on average.

Ideas for improvement

  • Refresh staging data every week.
  • Split any story above 5 points before planning.
  • One reviewer on duty each day, rotating through the team.

Next meeting

Sprint 15 retrospective in two weeks, same time — start by checking these three actions.

Illustrative example: an invented meeting. Names, organisations and figures are fictional; the structure is exactly what this template produces.

Template

Copy the retrospective template

Plain text you can paste into Word, Google Docs, Notion or an email — or download it as an editable Word file or a PDF.

Plain text
Word (DOCX)PDF
Sprint retrospective notes

Meeting: [ ]
Date and time: [ ]
Place / link: [ ]
Minutes taken by: [ ]
Sprint / period: [ ]
Facilitator: [ ]

Summary
[ ]

Participants
- [Name] — [role]
- [Name] — [role]

Agenda
1. [ ]
2. [ ]

What went well
- [ ]
- [ ]

What didn't go well
- [ ]
- [ ]

Ideas for improvement
- [ ]
- [ ]

Decisions
- [ ]
- [ ]

Action items
Owner | Task | Due
[ ] | [ ] | [ ]
[ ] | [ ] | [ ]
[ ] | [ ] | [ ]

Next meeting
[ ]
How it works

Generate these minutes from your recording

Skip the blank page: MinutesMaster writes “Retrospective” minutes from the recording itself.

  1. 1

    Bring the recording

    Upload an audio or video file (up to 2 GB), record in the browser or the mobile app, paste a YouTube or Google Drive link, or send the bot to a Zoom, Teams or Google Meet call.

  2. 2

    Choose “Retrospective”

    Pick the template when you upload, record or send the bot, or make it your default. Length, tone and sections can be adjusted for a single meeting.

  3. 3

    Review the draft

    The minutes are usually ready a minute or two after the upload finishes. Give each speaker their name once, check the decisions and owners, edit any field.

  4. 4

    Export or switch

    Download Word (DOCX) or PDF, or regenerate the meeting with another template for free — the earlier version stays under Versions.

Tips

Tips for retrospectives that change something

A retro is only as good as the actions that come out of it — and whether anyone checks them.

  • Start with last retro’s actions

    Open every retrospective by checking what happened to the previous actions. It shows the team that retros lead somewhere.

  • Describe the work, not the person

    “Reviews waited more than a day” invites a fix; “one person reviews too slowly” invites defensiveness. Blameless notes keep people talking openly.

  • Pick two or three improvements

    Ten ideas with no owners change nothing. Choose the few the team will actually try, give each an owner and a time frame.

  • Treat changes as experiments

    “Try it for two sprints, then decide” is easier to agree to than a permanent rule, and it puts the review on the calendar.

FAQ

Frequently asked questions

What are the three questions of a retrospective?
What went well, what didn’t go well, and what should we do differently? This template has one section for each, and the improvements the team commits to become action items with owners.
How long should a sprint retrospective take?
The Scrum Guide timeboxes it to at most three hours for a one-month sprint and says it is usually shorter for shorter sprints. For a two-week sprint, 45 to 90 minutes is common.
Can you give an example of sprint retrospective notes?
Yes — the example above shows a complete retro of a two-week sprint: what went well, what didn’t, the improvements, the decisions and the actions with owners, as MinutesMaster writes them from the recording.
How do you keep a retrospective blameless?
Talk and write about events and conditions, not individuals: what happened, what made it likely, what would prevent it. MinutesMaster writes this template in blameless wording.
Should retrospective notes be shared outside the team?
Usually the team keeps them, and only shares the actions that need help from others. In MinutesMaster a meeting stays private to your account unless you share it with a team workspace.
Can I use this template for a project post-mortem?
Yes. It suits post-mortems and lessons-learned sessions at the end of a project or after an incident. Add a section such as “Timeline” if you need one; extra sections can be added per meeting.
Is there a sprint retrospective template in Word?
Yes. Download it above as an editable DOCX or as a PDF, or copy the plain-text version into Word, Google Docs or your team’s wiki.

Related pages

Get the retro notes from your recording

Record the retrospective or send the bot, and the actions come out with owners. 5 free credits, no credit card.

Start freeSee pricing
  • 5 free credits
  • No credit card
  • No AI training on your data

Last updated