Agile Iteration (Sprint) Review Checklist
Use this framework to perform a review at the end of each iteration. An iteration review is conducted with the Product Owner to ensure all acceptance criteria of the work completed have been met. Following the review, the team then demonstrates completed functionality to showcase their work to interested stakeholders and/or customers.
How often should this be used?
On the last day of a Sprint.
Library
Categories
Agile Iteration (Sprint) Review
Attendees
Product Owner
Team
Scrum Master and/or Project Managers
Stakeholders
Preparation / Inputs
Working, tested software
Agenda
Review meeting agenda and guidelines
Purpose:
An iteration review is conducted with the Product Owner to ensure all acceptance criteria of the work completed have been met.
Following the review, the team then demonstrates completed functionality to showcase their work to interested stakeholders and/or customers.
Key Considerations:
- "Just say no" to PowerPoint slide decks or feature dissertations
- The Product Owner may decide not to accept certain functionality
Team walks through completed functionality with Product Owner
Team identifies any incomplete stories
The Product Owner moves and/or splits incomplete stories or backlog items into next iteration or back into product backlog if no longer a prioritiy
Product Owner closes out iteration and accepts appropriate functionality
Team demonstrates working software to interested stakeholders
Any open issues/impediments and action items are noted and assigned
Confirmed outputs
Final acceptance of completed functionality
Resolution to any incomplete items
Product backlog prepped
