Sprint retrospective notes template
Trippi Notes team · facts checked on 2026-10-01
Most retros fail the same way: the team agrees on changes, and nobody checks them at the next retro. This template starts with that check, and it does not let a change leave the room without an owner.
The template
Copy it into any editor that understands Markdown. The headings and the table come through as they are.
# Retro — [team] — [sprint / date] ## Last retro's actions - [action] — [owner] — done / not done / dropped ## Went well - ## Went badly - ## What to change - ## Agreed changes - ## Actions | Action | Owner | By when | |--------|-------|---------| | | | | ## Changes nobody owns yet -
For Word or Google Docs
The same template as plain text. Paste it into a new document, then turn the first line and the section names into headings if you like. There is no file to download: you paste it, and it is yours.
RETRO — [TEAM] — [SPRINT / DATE] Last retro's actions - [action] — [owner] — done / not done / dropped Went well - Went badly - What to change - Agreed changes - Actions Action — Owner — By when - Changes nobody owns yet -
What each part is for
Last retro’s actions
Five minutes, at the start. If the same item is "not done" twice, talk about why, or drop it on purpose.
Went well / went badly
Facts, not people. "Two releases were rolled back" rather than "QA missed things".
What to change
Ideas. Not all of them will be agreed.
Agreed changes
The process changes the team actually decided on. Usually one to three.
Actions
Each agreed change, with the person who volunteered or was named, and a date.
Changes nobody owns yet
If no one takes it, it goes here, and it is the first question at the next retro.
The Scrum Guide says the purpose of the Sprint Retrospective is "to plan ways to increase quality and effectiveness", and time-boxes it to at most three hours for a one-month sprint. Shorter sprints usually mean shorter retros.
How to fill it in five minutes
- 1Before: Copy last retro’s actions into the first section. Do not add anything else.
- 2During: Write items under went well, went badly and what to change as people say them. One line each.
- 3Before closing: Read the agreed changes out loud and ask "who takes this?" for each one.
- 4After: Share the notes, and put the actions where the team tracks its work so they are seen during the sprint.
A filled example
Retro — Mobile team — Sprint 41
Last retro’s actions
- Add a review checklist — Ana — done
- Shorter planning — Bruno — not done (second time)
Went well: release on time; checklist caught two bugs.
Went badly: planning ran 2 hours; design arrived mid-sprint.
Agreed changes: planning gets a written agenda, 60 minutes.
Actions
Write the planning agenda — Bruno — before Sprint 42 planning
Changes nobody owns yet
- Design handoff before the sprint starts
Let it fill itself
This is the same shape Trippi Notes uses for its Retrospective summary. Trippi Notes listens to the meeting tab in Chrome — Google Meet, Zoom in the browser or Microsoft Teams in the browser — after one click on its icon, and writes the transcript with speaker names and times. After the call you pick the Retrospective template and build the summary with one click. The template tells it to look for what went well, what went badly and what to change; decisions are the process changes agreed, every task needs an owner, and a change nobody owns goes to open questions. The result comes back in the usual parts — overview, decisions, tasks with owners, open questions — in your language, even if the call was in another one.
From there you copy it into this layout, export it as Markdown or plain text, or ask a question about the meeting and get quotes that jump to the moment. Open tasks stay in one action items list across meetings, so last time’s agreements are there when the next one starts.
Summary templates other than the general one, and your own request, are part of the paid plans. It only hears calls in the browser, not desktop apps or phones. Nothing joins the call, so nobody sees a bot in the list of people. Tell them you are taking notes anyway — how to ask.
FAQ
Asked about this.
What are the three retrospective questions?+
Most teams use some form of: what went well, what went badly, what to change. Any format works if it ends with owned actions.
How long should a retro take?+
The Scrum Guide caps it at three hours for a one-month sprint. For a two-week sprint, an hour is common.
Who should take retro notes?+
Not the facilitator. Rotate it, or let a tool draft them while the facilitator runs the room.
Should retro notes be shared outside the team?+
Usually only the actions. The rest is for the team, so people can speak openly.
Read next
Let the notes fill themselves.
Trippi Notes is in the Chrome Web Store. One click on the icon when the call begins, and nothing before that.