1. Sprint Review Results
Example Template

2. License and Contact Details
This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit To see the blog post about this template and download the PowerPoint version please visit: agil8
© agil8 2014

3. About the Sprint Review
To download the PowerPoint version of this template please visit
A Sprint Review is held at the end of each Sprint to inspect the Product Increment and, if required, adapt the Product Backlog. The Sprint Review meeting is timeboxed to 1 hour for each week of the Sprint. The Scrum Team and stakeholders collaborate to understand what happened in the Sprint, what changes occurred and what might be done next. The Sprint Review is an informal meeting, the intention of which is to create transparency, feedback and collaboration.
Within the Sprint Review meeting:
The Product Owner identifies what has been “Done” and what has not been “Done”
The Development Team describes how the Sprint went: what went well, what problems it had, and how it addressed them (they will hold a Sprint Retrospective following this meeting)
The Product Increment is demonstrated, questions about it are fielded by the Scrum Team and any potential new Product Backlog Items are identified
The Product Owner leads a review of the Product Backlog, drawing attention to any changes since the last Sprint Review
The Product Owner presents projected completion dates based on progress to date and everyone in the meeting collaborates to determine if the Product Backlog should be changed and what to do next
© agil8 2014

4. About this Template
People and interactions should be valued over processes and tools … but it is still a good idea to capture the results of key meetings so that decisions and the rationale behind them are not lost and can be communicated to those not present
This template should be adapted for your own context
It is presented in PowerPoint for the sake of convenience and because many teams use it
Any suitable tool can be used instead: from a white board or flip charts with a digital camera to record them, to direct entry into a backlog management and collaboration software tool
© agil8 2014

5. Sprint Review
Team name: Date of review: Time: Venue: Product Owner: ScrumMaster: Sprint Goal:
Stakeholders present:
Team members present:
© agil8 2014

6. Product Backlog Item Approval
Ref
Product Backlog Item Name and Type (e.g. Functional/NFR/New Feature/Maintenance/Spike/Dev Environment)
No of ‘Points’
Done?
Y/N? 1 2 3 4 5 6 7 8 9 10 11
© agil8 2014

7. Development Team View
Velocity this Sprint: Typical historical velocity:
What went well during the Sprint?
Problems encountered?
How solved?
© agil8 2014

8. Product Backlog Items to be Demo’d
Ref
Product Backlog Item Name
Comments/Questions 1 2 3 4 5 6 7 8 9 10 11
© agil8 2014

9. Changes to Product Backlog In this Sprint
Changes to Full Planned Scope
Points estimated in Full Planned Scope at start of Sprint:
Points estimated in Full Planned Scope at end of Sprint:
Reason/s for Change:
Changes to Minimum Scope
Points estimated in Minimum Scope at start of Sprint:
Points estimated in Minimum Scope at end of Sprint:
Reason/s for Change:
© agil8 2014

10. Product Backlog Review
Likely completion dates based on progress so far:
Full planned scope: dd/mm/yy
Minimum scope: dd/mm/yy
Agreed adjustments to overall Product Backlog:
© agil8 2014

11. Probable Product Backlog Items for Next Sprint
Ref
Product Backlog Item Name
Comments 1 2 3 4 5 6 7 8 9 10 11
© agil8 2014