What This Template Is For
The sprint review is where your team shows what they built and collects feedback from stakeholders. It is not a status update. It is a live demo followed by an honest conversation about what shipped, what did not, and what should change next.
Most sprint reviews fail because they are either a slideshow of Jira tickets or an unstructured free-for-all where stakeholders hijack the agenda. This template gives you a repeatable structure: pre-meeting prep, a timed demo agenda, a feedback capture framework, and a next-sprint alignment discussion. If your team is running Scrum, pair this with the sprint planning template for a complete sprint cadence.
When to Use This Template
- End of every sprint: Run the review on the last day, before the retrospective.
- After a major milestone: Demo a significant feature to a wider audience.
- When stakeholder alignment is slipping: Use the review to reset expectations with real working software.
- New team onboarding: Establish the review ritual early so stakeholders know what to expect.
Step-by-Step Instructions
Step 1: Prepare the Demo (30 minutes before meeting)
Pick 3-5 items to demo. Each demo should show working software, not slides. Assign a presenter for each item and rehearse transitions.
- ☐ Select 3-5 completed stories to demo
- ☐ Assign a presenter for each item
- ☐ Prepare test data or staging environment
- ☐ Confirm screen share and audio work
- ☐ Send the agenda to stakeholders 24 hours in advance
Step 2: Run the Review (45-60 minutes)
Follow the timed agenda below. The facilitator keeps time and manages the Q&A queue.
- ☐ Open with sprint goal recap (5 min)
- ☐ Demo each completed item (25-35 min)
- ☐ Capture feedback in writing during each demo
- ☐ Review what was not completed and why (5 min)
- ☐ Discuss backlog adjustments based on feedback (10 min)
Step 3: Follow Up (15 minutes after meeting)
Document the feedback and share it with the team before the retrospective.
- ☐ Summarize feedback into actionable items
- ☐ Add new stories to the backlog from feedback
- ☐ Share meeting notes with all attendees
- ☐ Flag any priority shifts for next sprint planning
The Sprint Review Template
Sprint: [Sprint number]
Date: [Review date]
Sprint Goal: [One sentence]
Facilitator: [Name]
Attendees: [Team members, stakeholders]
Sprint Summary
| Metric | Value |
|---|---|
| Stories committed | [X] |
| Stories completed | [Y] |
| Story points committed | [X pts] |
| Story points completed | [Y pts] |
| Sprint goal achieved? | [Yes / Partially / No] |
Demo Agenda
| # | Item | Presenter | Time | Demo Notes |
|---|---|---|---|---|
| 1 | [Feature/story title] | [Name] | 5 min | [What to show] |
| 2 | [Feature/story title] | [Name] | 5 min | [What to show] |
| 3 | [Feature/story title] | [Name] | 5 min | [What to show] |
Items Not Completed
| Story | Reason | Plan |
|---|---|---|
| [Title] | [Blocked / Carry-over / Descoped] | [Next sprint / Needs refinement] |
Stakeholder Feedback
| Feedback | From | Priority | Action |
|---|---|---|---|
| [Feedback item] | [Name] | [High / Med / Low] | [New story / Backlog / Note] |
Next Sprint Preview
Proposed sprint goal: [One sentence]
Key items under consideration: [Brief list]
Example
Sprint: Sprint 14 | Date: Mar 4, 2026
Sprint Goal: Users can schedule and manage recurring reports from the dashboard.
Facilitator: Alex (PM)
Sprint Summary
| Metric | Value |
|---|---|
| Stories committed | 6 |
| Stories completed | 5 |
| Story points committed | 28 |
| Story points completed | 24 |
| Sprint goal achieved? | Yes |
Demo Agenda
| # | Item | Presenter | Time |
|---|---|---|---|
| 1 | Recurring report scheduler UI | Dana (Eng) | 7 min |
| 2 | Email delivery for scheduled reports | Raj (Eng) | 5 min |
| 3 | Report template selector redesign | Kim (Design) | 5 min |
Items Not Completed
| Story | Reason | Plan |
|---|---|---|
| CSV export for scheduled reports | Blocked by third-party API rate limits | Carry to Sprint 15 |
Stakeholder Feedback
| Feedback | From | Priority | Action |
|---|---|---|---|
| Add Slack notification option for report delivery | VP Sales | High | New story for Sprint 15 |
| Show report history in the scheduler view | Customer Success Lead | Med | Add to backlog |
Tips
- Demo working software, not slides. Stakeholders trust what they can see running. If something is not demoable, it is not done.
- Time-box each demo to 5-7 minutes. Long demos lose the audience. Show the happy path, mention edge cases, and move on.
- Capture feedback in real time. Assign someone to take notes during the review. Verbal feedback that is not written down disappears by Monday.
- Separate the review from the retrospective. The review is about the product (what we built). The retro is about the process (how we built it). Mixing them dilutes both. For more on agile ceremonies, check the Stakeholder Management Handbook.
- Invite the right stakeholders. Include people who can give actionable feedback, not just executives who want a status report.