Sprint Review

Purpose

The Sprint Review is a critical Scrum event held at the end of each sprint. Its primary purpose is to inspect the increment and adapt the product backlog if needed. This meeting is an opportunity for the Scrum Team and stakeholders to review what was accomplished during the sprint and collaborate on what to do next.

Review the work completed during the sprint and demonstrate the increment to stakeholders.

Collect feedback from stakeholders to ensure the product is evolving in the right direction and meeting their needs.

Update the product backlog based on feedback, changes in market conditions, or new information.

Discuss and plan the next steps, aligning on priorities and goals for future sprints.

Attendees

• Development Team — to present the increment and discuss what was accomplished
• Product Owner — to facilitate the review, gather feedback, and update the product backlog
• Scrum Master — to facilitate the meeting and ensure it adheres to Scrum principles
• Stakeholders — including business representatives, customers, and other interested parties to provide feedback and input

Input

• Increment — the completed work from the sprint that is potentially shippable
• Sprint Backlog — the list of items that were committed to at the beginning of the sprint
• Product Backlog — the updated list of items, including those not completed in the sprint
• Feedback — insights and feedback from previous reviews or other sources

• Open tickets remaining in the current sprint, with an agreed next action and end-of-sprint comment on each ticket.
• Tickets added mid-sprint, including the reason they were introduced and who requested or approved the change.
• Tickets deployed to production and sprint goals with end-of-sprint status marked as Completed, Part Completed or Not Completed.

Outputs

• Reviewed Increment — validation of the work completed, and identification of any adjustments needed
• Updated Product Backlog — adjustments to the backlog based on feedback and new information
• Feedback and Insights — collected input from stakeholders to inform future sprints
• Next Steps and Priorities — agreed-upon next steps and updated priorities for the upcoming sprint planning

• Clear decision on whether open tickets are brought into the next sprint, moved to a future sprint or returned to backlog.
• Documented explanation for missed or carried-over sprint goals, including blockers, dependencies, scope changes or testing delays.
• Actions, risks or decisions to raise with Platform Owners during the sprint review and planning alignment session.

Responsibilities

• Facilitate the review and gather feedback
• Present the updated product backlog
• Ensure that stakeholder feedback is incorporated into future planning

• Facilitate the meeting and ensure it runs smoothly
• Help resolve any impediments and ensure adherence to Scrum principles
• Support the Product Owner and Development Team as needed

• Present the completed work and demonstrate working software developed in the sprint
• Present the work not done
• Discuss what went well, what problems were encountered, and how they were solved
• Collaborate with stakeholders on feedback and future planning

• Provide feedback on the increment
• Share insights and discuss priorities
• Collaborate on the next steps and future goals