Sprint Review Meeting Agenda
A sprint review is a meeting at the end of each sprint where the Scrum team shows key stakeholders what it delivered and they decide together what to do next. This sprint review meeting agenda fits a two-week sprint into 60 minutes and ends with an updated product backlog that reflects what everyone learned.
Agenda
60 min · 5 parts
- 0:00Sprint recap5 minThe sprint goal, what got done and what didn't
- 5:00Demo25 minWorking product, done items only, and stakeholders trying it themselves
- 30:00Feedback15 minWhat stakeholders think, and what has changed around the product
- 45:00Backlog update10 minNew items, new priorities and progress toward the product goal
- 55:00What's next5 minThe likely focus of the next sprint and open questions
Free to start. Guests join from a link, no account needed.
- Length
- 60 min
- How often
- At the end of every sprint, before the sprint retrospective.
- Who attends
- The Scrum team and key stakeholders: customers, users, managers, sales or support, anyone whose feedback shapes the product.
- You leave with
- Feedback on the work the sprint delivered and a revised product backlog that shows what will likely come next.
The agenda, part by part
How to run a sprint review meeting
1. Sprint recap
5 minThe product owner restates the sprint goal and says plainly which items are done and which are not. Done means meeting the definition of done, not almost finished. An honest recap sets expectations before the demo.
Ask: Did we meet the sprint goal, and what didn't make it?
2. Demo
25 minThe developers show working software, not slides, and only what meets the definition of done. Tell it as a story: the user's problem first, then the product solving it. Hand control to a stakeholder when you can; watching someone use it reveals more than any explanation.
Ask: What would you try first if this were in your hands today?
3. Feedback
15 minAsk stakeholders what they think, then widen the view: what has changed with customers, the market, the budget or the timeline. The Scrum Guide calls the review a working session, and this is where most of that work happens. Capture each point as it comes, without debating it.
Ask: What has changed for you since the last review?
4. Backlog update
10 minThe product owner walks through how the feedback changes priorities: new items, items that move up and items that can go. Discuss progress toward the product goal and any forecast for a release. If the team learned anything, the backlog should look different when the meeting ends.
Ask: Given what we heard, what matters most now?
5. What's next
5 minSummarize what the next sprint will probably focus on and which questions are still open. Confirm who will follow up with which stakeholder. The next sprint goal is set in sprint planning, so treat this as a direction, not a promise.
Ask: What do we need to know before we plan the next sprint?
Sprint review questions to ask stakeholders
- Does this solve the problem you described?
- What would stop you from using this today?
- What did you expect to see that's missing?
- What has changed for your team or your customers since the last review?
- Which item in the backlog matters most to you now?
- Is there anything we should stop building?
- Who else should see this before it's released?
Example: a review with customers in the room
A team building online booking for a group of clinics invites two clinic managers and the support lead to its review.
Notes
- Goal met: patients can reschedule an appointment from the confirmation email.
- Not done: text message reminders, still waiting on the provider's approval.
- Clinic manager: reception staff need to see who rescheduled, not just the new time.
- Support: most calls are about cancelling, not rescheduling.
- Backlog: cancellation flow moves up; reminder settings move down.
Action items
- Amara (product owner): write the cancellation stories, by Thursday.
- Jonas: set up test accounts for both clinic managers, by Friday.
Ways to adapt it
Many stakeholders
Keep the same sprint review template, but run the demo as stations, one per feature or team, and let people move between them. Then come back together for feedback and the backlog.
Remote review
Share a short list of what's done the day before and collect feedback in a shared doc during the call, so quieter stakeholders can write instead of speak.
One-week sprints
Shorten the sprint review agenda to 30 minutes: a quick recap, a demo of the most important item and the rest of the time on feedback.
Common mistakes
Showing slides instead of the product.
Instead: Demo the working product. If something can't be shown, it probably isn't done.
Demoing work that isn't done.
Instead: Only show items that meet the definition of done, and say clearly what is still in progress.
Turning it into a presentation with no discussion.
Instead: Keep at least a third of the time for feedback and backlog changes. The review is a working session.
Inviting no stakeholders.
Instead: Invite the people who use, sell, support or pay for the product. A review with only the team is a rehearsal.
Sprint review vs sprint retrospective
The sprint review looks at the product: what the team built, what stakeholders think of it and what to do next. The sprint retrospective looks at the team: how it worked and what to change in its process. The review comes first and includes stakeholders; the retrospective follows, with the Scrum team only, and closes the sprint.
Run it in Edworking
Your agenda keeps the meeting on time
Start a video meeting from any template. Edworking turns the agenda into the structure of the call, so nobody has to watch the clock.
Live agenda
A timer for every part
Everyone sees the agenda and how long is left in each part, with a clear moment when the meeting moves on.
AI notes
Notes that follow the agenda
AI takes the notes part by part and writes the summary and action items when the call ends.
Tabs in the call
Your work on screen, no sharing
Open docs, tasks and files as tabs in the call. Everyone sees the same thing without anyone sharing a screen.
Guests
Anyone can join from a link
Free to start. Clients, candidates and guests join from a link, with no account needed.
Frequently asked questions
The Scrum Guide sets a maximum of four hours for a one-month sprint, and shorter sprints usually need less. For a two-week sprint, an hour or two is usually enough.
The Scrum team and the key stakeholders the product owner invites: customers, users, managers, sales or support. Without stakeholders, the meeting loses its main purpose, which is feedback.
No. The Scrum Guide says the team should avoid limiting it to a presentation. The demo starts the conversation, but the point is to inspect the result together and adapt the product backlog.
A recap of the sprint goal, a demo of the work that is done, stakeholder feedback, an update to the product backlog and a look at what comes next. Give the demo and the feedback most of the time.
The product owner usually hosts it and the developers demo their own work. The Scrum Master helps keep it within its timebox and focused on feedback.
More meeting agenda templates
Sprint Retrospective Template
Look back on the sprint together and agree on the one or two things to change.
5 parts
Sprint Planning Meeting Agenda
Agree on the sprint goal, choose the work and plan how the team will deliver it.
5 parts
Daily Standup Meeting Agenda
A 15-minute daily check-in on what moved, what's next and what's in the way.
3 parts