Template

Sprint review template

At the end of a sprint: show what was finished, hear what the people it is for think, and change what comes next.

60 minutesFor Product owners, scrum masters and the people the work is forAgenda room
Change the agenda first

The agenda, with a time for each part

  1. What we set out to do this sprint5 min
    • What was the goal, and did we meet it?
  2. Show the finished work25 min
    • Can you try it yourself, right now?
    • What did you expect it to do that it did not?
  3. What was not finished, and why8 min
    • What stopped it, and does it still matter?
  4. What has changed outside the team8 min
    • What have customers, the market or the budget done since last time?
  5. What comes next10 min
    • Given what we just saw, is the top of the list still right?
  6. Dates and anything promised4 min
    • Is anything we told people now at risk?

How the notes read afterwards

A made-up example, so you can see the shape. In a real call each line carries the words that were said and who said them.

Goal. People can pay by invoice. Met.

Shown. Lena, from finance, raised an invoice in two minutes — and could not find where to add a purchase order number.

Not finished. Reminder emails: the template is waiting on legal.

Next. The purchase order field moves to the top of the list.

Running it well

Ways to change it

Thirty minutes, one-week sprintGoal, show the work, what comes next. Drop the rest.
Several teams at onceEach team gets ten minutes to show one thing. Questions go in the chat and are answered afterwards.

When to skip it. When nothing was finished. Say so in a message, and spend the hour finishing.

Questions

What is a sprint review?

A meeting at the end of each sprint where the team shows the work it finished to the people it is for, and the plan for what comes next is adjusted.

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

The review looks at the product: what was built and what to build next. The retrospective looks at the team: how it worked and what to change.

Who should attend a sprint review?

The team, the product owner, and the people who will use or pay for the work. Without them it is a status meeting.

What happens in the room

Everybody joins from the link, with no account. The agenda sits beside the call and each item fills in with what was said about it, under the name of the person who said it.

More templates

Project kickoffWhy the project exists, what done means, and who owns what — agreed on day one.Sprint retrospectiveWhat went well, what did not, and the one or two changes you will actually make.Sprint planningOne goal for the sprint, the work that serves it, and who takes what.Incident postmortemWhat happened, why, and what changes so it does not happen again — without blaming anybody.Product roadmap reviewWhat is being built next and why, what moved since last time, and what was cut to make room.Design reviewOne design, shown early, with the questions the designer actually wants answered.Backlog refinementGo through what is coming next, make each item small and clear enough to start, and throw out what will never be done.User research interviewOne customer, in their own words: what they were trying to do, what they did, and where it went wrong.

All 60 templates →

Try Meetful

Meetings that take their own notes

Free video meetings in the browser: every line of the transcript under the name of who said it, and the summary and action items when you hang up. Nothing to install — guests just open the link.

Try Meetful freeSee what it does