Prompt Notebook

Retrospectives · Agile · Meetings

How to run a sprint retrospective, with a filled-in example

By T. Krause

A sprint retrospective is the meeting at the end of a sprint where the team decides what to change about how it works. Here is a one-hour agenda, how to stop the loudest voice setting it, a filled-in example for an invented team and a free template.

To run a sprint retrospective, get the whole team together at the end of the sprint for about an hour. Start by checking whether the actions from the last retro happened. Then give everyone five minutes to write notes on their own about what went well and what didn't, group the notes, and vote on which problems to work on. Spend most of the time on the top two or three, and leave with no more than three actions, each with a name and a date.

That's the whole method. The rest of this guide covers each step, a one-hour agenda, the mistakes that turn retros into a ritual nobody looks forward to, and a complete example for an invented team. If you want a page with the headings already in place, copy our free sprint retrospective template.

What a sprint retrospective is for

The Scrum Guide, in its November 2020 version, says the purpose of the Sprint Retrospective is "to plan ways to increase quality and effectiveness". The team looks at how the last sprint went and picks the changes that would help most. The retro is the last event of the sprint.

So the output of a retro is a change to how the team works next sprint. A list of complaints doesn't count, and neither does a pleasant chat. If the team leaves with nothing to do differently, the hour was spent on venting.

You don't need to run Scrum to use this. Any team that works in fixed cycles can hold the same meeting at the end of each one.

Before the meeting

Pick who runs it. Someone has to keep time and keep the discussion on the problem being discussed. Rotate the job so it doesn't always fall to the team lead or the Scrum Master, and so one person's habits don't shape every retro.

Book an hour. The Scrum Guide caps the retrospective at three hours for a one-month sprint and says shorter sprints usually need less. For a two-week sprint, an hour is enough for most teams of five to eight people. If you keep running out of time, the problem is usually too many topics, not too few minutes.

Prepare the page. Copy the last retro's actions to the top of the new page, then add empty headings for the notes. Share it with edit access before the meeting so nobody waits for a link.

How to run it, step by step

1. Open with the ground rule

Read one sentence aloud at the start. A common choice is the Prime Directive from Norm Kerth's book Project Retrospectives, quoted on the Agile Retrospective Resource Wiki: "Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."

You don't have to use those words. The point is to say out loud that the retro is about the work and the system around it. Nobody is on trial. People who expect blame write vague notes, and you can't fix a vague note.

2. Check last time's actions

Go through the actions from the previous retro one by one. Each is done, carried over with a new date, or dropped with a reason. This takes five minutes and it's the step most teams skip. Skip it and the team soon learns that retro actions don't matter, because nobody ever asks about them again.

If an action keeps being carried over, say so. Usually it's too big for one sprint, or the team cares about it less than it thought. Either way, the team should know.

3. Write notes in silence

Give everyone five minutes to add notes on their own under two headings, what went well and what didn't go well. One point per note, written so someone who wasn't there could understand it. "Staging" says nothing. "Staging was down for most of Tuesday and we couldn't test the release" is a note you can act on.

Writing alone first matters more than any other part of the format. When people talk first, the first opinion spoken sets the topic, and quieter people end up agreeing rather than adding. Five minutes of silence gets you everyone's view.

4. Group and vote

Read the notes aloud and merge the ones that describe the same thing. Then give everyone three votes to spend on the problems they most want to fix. They can put all three on one note. Add the count next to each note and sort by votes.

Only the top two or three problems get discussed. The rest stay on the page, and if they matter, they'll come back next sprint with more votes.

5. Find causes and ideas

Take the top problem and ask what caused it. Keep asking until you reach something the team can change. "Tickets came back from QA" is the symptom. "Nobody checked the acceptance criteria before work started" is something you can fix. Collect ideas under each problem, then move on to the next before time runs out.

6. Agree on actions

Turn the best ideas into actions. Each action needs one owner, a date and a description specific enough that everyone will agree on whether it happened. "Improve communication" fails that test. "Priya agrees a reply time with the clinic managers by Friday" passes it.

Stop at three actions. A team that commits to seven changes in a two-week sprint will finish one or two and feel bad about the rest.

7. Close with a mood check

Ask everyone to rate the sprint from 1 to 5 and note the average. One number won't tell you much, but the trend over several sprints will. A score that drops three sprints in a row is worth a conversation even if the notes look calm.

A one-hour agenda

TimeStep
0 to 5 minOpen, read the ground rule
5 to 10 minCheck last retro's actions
10 to 15 minWrite notes in silence
15 to 25 minRead aloud, group, vote
25 to 45 minCauses and ideas for the top two or three problems
45 to 55 minAgree actions with owners and dates
55 to 60 minMood check and close

A filled-in example

The team, the people and the dates below are invented. Larkfield is a five-person team building an online booking app for a small chain of physiotherapy clinics. Priya Shah is the product owner, Aisha Okafor and Marek Nowak are developers, Elena Rossi is the designer and Tom Reid is a developer who ran this retro. Sprint 14 lasted two weeks and ended on Thursday 22 October 2026. The retro took an hour that afternoon.

Retro: sprint 14, Thursday 22 October 2026

Ground rule. Everyone writes notes alone for five minutes, then we group and vote. Three votes each.

Last retro's actions

  • Marek: add an end-to-end test for the booking flow to the build. Done, and it caught a broken time slot picker on day three.
  • Priya: agree a reply time with the clinic managers. Not done, carried over.

What went well

  • The new end-to-end test caught the time slot bug before any clinic saw it
  • Online payment for bookings shipped on the planned day
  • Pairing Elena and Aisha on the cancellation screen saved a round of design changes

What didn't go well

  • Two stories reached review before their designs were signed off, and both went back for changes (6 votes)
  • The test server reset itself overnight twice and wiped the test bookings (4 votes)
  • Stand-ups ran to about 25 minutes most days (3 votes)
  • Nobody owned replies to the clinic managers' questions, and two waited over a week (2 votes)

Ideas

  • Add "design signed off" to the checklist a story needs before it can be picked up
  • Create test bookings from a script after every reset, so a reset costs minutes
  • Agree a reply time with the clinic managers and name one person for questions

Actions

  • Elena: add "design signed off" to the ready checklist, in place for sprint 15 planning on Monday 26 October
  • Aisha: script that creates test bookings after a server reset, by Wednesday 28 October
  • Priya: agree a two working day reply time with the clinic managers, by Friday 30 October. Carried over from sprint 13

Mood

Scores of 4, 3, 3, 4 and 2. Average 3.2, down from 3.6 last sprint.

Why this example works

The check of last time's actions shows the previous retro had a result, a test that caught a real bug, and it shows one action that slipped. The clinic reply problem only got two votes, but the team kept the carried-over action and gave it a date instead of quietly dropping it. Stand-ups got three votes and no action. That's fine. With three actions already agreed, the team left it for next time rather than overload the sprint. The votes add up to fifteen, three for each of the five people. Every action has one name and one date, so the next retro can check each one in a minute.

Common mistakes

Talking before writing. If the retro opens with "so, how did it go?", you get the opinions of the two people who speak first. Write first, talk second.

Never checking last time's actions. This is the fastest way to make a retro pointless. If nothing ever happens to the actions, people stop suggesting them.

Too many actions. Three is plenty. Pick fewer if the actions are big.

Actions owned by "the team". When everyone owns an action, nobody does. Put one name on it.

The same format every time. After ten retros with the same headings, people write the same notes. Swap the format now and then. Start, stop, continue asks what the team should start doing, stop doing and keep doing. A sailboat retro asks what pushed the team forward and what held it back. The steps stay the same.

Managers who judge the notes. If someone outside the team reads the page to find out who caused the delays, the next retro will be very polite and useless. Decide up front who reads the page.

Retrospective, postmortem and status update

A retro looks back at a normal sprint. When one thing went badly wrong, such as an outage or a failed launch, it deserves its own meeting with a timeline and causes. Our guide on how to write a postmortem covers that format.

Retro actions sometimes change something people outside the team will notice, like a new reply time for clients. Put those in your next weekly status update so they hear it from you. And if your team already keeps meeting minutes for other meetings, the retro page does the same job for this one. It records what was decided and who owns each action.

Running it in Prompt Notebook

Prompt Notebook is ours, so read this part with that in mind. The sprint retrospective template has a purple callout with the ground rule about silent notes and three votes each, then headings for last retro's actions, what went well, what didn't go well, ideas, actions and mood. It comes filled in with a sample retro so you can see each section in use.

Share the page with edit access so everyone can add their notes during the silent five minutes. Write actions as to-dos with a name and a date so they show as checkboxes, and tick them off at the start of the next retro. When you're done, select the page and use Ask AI to summarise it for people who weren't there.

Frequently asked questions

How long should a sprint retrospective be?

The Scrum Guide sets a maximum of three hours for a one-month sprint and says shorter sprints usually need less. For a two-week sprint, an hour works for most teams. If you need more time, you're probably trying to discuss too many problems.

What questions should you ask in a sprint retrospective?

Start with two: what went well, and what didn't go well. For the top problems, ask what caused them and what you could try next sprint. Then ask who will do it and by when. Open with whether last retro's actions happened.

Who should attend a sprint retrospective?

The whole team that did the work in the sprint. In Scrum, that's the Scrum Team: the Scrum Master, the Product Owner and the Developers. Leave people outside the team out of it, because they make it harder to talk openly about what went wrong.

What is the difference between a sprint review and a sprint retrospective?

The sprint review looks at what the team built. The team shows it to stakeholders and they discuss what to do next. The retrospective looks at how the team worked, and the team holds it on its own after the review.

What if the team says there's nothing to improve?

Look at the last retro's actions and the mood scores first. If both look fine, ask a narrower question, such as "what slowed you down most this sprint?" Most teams have an answer to that one. A short retro with one small action is still worth having.

Try it on your own notes

Prompt Notebook is free, with unlimited pages. Type one sentence and the AI drafts the first version.

Cookies and storage

Prompt Notebook needs one cookie to keep you signed in. Accepting turns on Google Analytics and Google's reCAPTCHA spam check on the contact form, and declining keeps the form working. Nothing optional runs until you choose.

Read the privacy notice