BlogGuide
Sprint Review Template: Free One-Page Summary, With Example
A free one-page sprint review template for agile teams, the 6 parts stakeholders want to see, a worked example with points planned against done and velocity, and the mistakes that turn reviews into status meetings.
By MakeOnepagers Team
Updated · 4 min read
A sprint review template puts one sprint on a single page: points and stories planned against what got done, what shipped, how velocity is trending, what carried over and why, and the goal for the next sprint. The sprint review is the meeting where stakeholders see what the team built. A one-page sprint review summary gives them the facts before the demo starts, and it is the record they read when they miss the meeting. Below are the six parts stakeholders want to see, a free template you can copy and a worked example.
One‑Pager examples
Real One-Pagers made with MakeOnepagers. Open any one to edit it as your own.
Sprint Review with WorkstreamsEdit for free(opens in a new tab)
RetrospectiveEdit for free(opens in a new tab)
Weekly Status ReportEdit for free(opens in a new tab)
Project Status ReportEdit for free(opens in a new tab)
Product RoadmapEdit for free(opens in a new tab)
Multi-Team Sprint ReviewEdit for free(opens in a new tab)
The example was made with MakeOnepagers. It opens as a template you can edit for free: every word, chart and color.
What is a sprint review?
A sprint review is the meeting at the end of a sprint in Scrum, where the team shows what it completed and stakeholders give feedback. It is different from the retrospective, which is the team's own meeting about how it worked.
The one-page summary supports the review. It shows the numbers, so the meeting can spend its time on the demo and the feedback.
The 6 parts of a sprint review
- The sprint, team and dates.
- At a glance: points done against planned, stories shipped, items carried over.
- Planned against done: points, stories and bugs fixed.
- What shipped, in words a customer would recognise.
- Velocity over the last six sprints.
- Next sprint goal and what carried over, with the reason for each.
A free sprint review template
Copy this into a document, or open the example below and edit it.
| Part | What to write, with an example |
|---|---|
| Title | Sprint, team, dates. Sprint 24 Review, payments squad, 23 Sep to 6 Oct |
| At a glance | 3 numbers. 34 of 40 points done |
| Planned against done | Points, stories, bugs. Stories 9 of 11, bugs fixed 12 against 10 |
| Shipped | 3 to 5 items. Saved cards at checkout |
| Velocity | Last 6 sprints. 24, 29, 26, 32, 31, 34 |
| Next sprint goal | 3 items with a target. Checkout errors: cut below 0.5% |
| Carried over | Each with a reason. Fraud rules export, 2 points left |
Sprint review example
Edit this template
A two-week sprint on one page: the numbers first, then what shipped and what comes next.
What to copy:
- Planned against done for three measures: points 34 of 40, stories 9 of 11, bugs fixed 12 against 10. One number alone hides whether the team over-planned or under-delivered.
- Shipped items named the way users see them: saved cards at checkout, refund status emails, 3DS retry. Stakeholders recognise those; they do not recognise ticket numbers.
- Six sprints of velocity: 24, 29, 26, 32, 31, 34. One sprint is noise; six is a trend.
- Carried-over items with the reason: "Apple Pay on web, waiting on the domain check." Nobody has to ask why it slipped.
Edit for free: sprint review template.
Sprint review or sprint retrospective?
| Sprint review | Sprint retrospective | |
|---|---|---|
| Who attends | Team and stakeholders | The team only |
| About | The product: what was built | The process: how the team worked |
| Output | Feedback and next priorities | Two or three changes to try |
How to run a sprint review in 6 steps
- Fill in the numbers before the meeting: planned, done, carried over.
- List what shipped in user language.
- Send the page a day ahead, so the meeting can skip the numbers.
- Demo the shipped items, in the order customers would use them.
- Collect feedback and agree what changes in the backlog.
- Set the next sprint goal and add it to the page.
Have sprint data in a tracker export or a spreadsheet? Drop it into the free AI One-Pager generator and get it back as a designed sprint review.
Sprint review mistakes
- A status meeting. Reading the board aloud wastes everyone's time. Show the product.
- Ticket numbers instead of features. Stakeholders cannot react to "PAY-2231."
- Hiding what slipped. Carried-over work with a reason builds trust. Missing work without one does not.
- No goal for the next sprint. The review should end with what comes next.
Make your sprint review
Open the free sprint review template and put in your sprint, or drop your tracker export into the free AI One-Pager generator and get a finished sprint review back.
Frequently asked questions
What should a sprint review include?
The sprint and dates, points and stories planned against done, what shipped, velocity, what carried over and why, and the next sprint goal.
How long should a sprint review be?
For a two-week sprint, the meeting usually runs up to an hour, and the summary fits on one page.
Who attends a sprint review?
The Scrum team, the product owner and stakeholders such as managers, customers or other teams who depend on the work.
What is a good sprint velocity?
There is no universal number. A good velocity is a steady one, because it lets the team plan reliably.
