Sprint Review
Last updated
Last updated
Goals
The fifth process step in the Application Development process is sprint review. The goal of the sprint review, as stated in the Scrum Guide, is to evaluate the results of the sprint and identify potential changes. The progress made toward the product goal is discussed as the scrum team presents the results of their work to important stakeholders. The important part here is that this is a continuous process step. And it is a meeting at the end of every sprint. 2. Scope
Working instruction covers enterprise application employees in Europe.
Responsibilities
Product Owner: Participates in the meeting.
Manager: He can show the overall progress of the project during this meeting.
Scrum Development Team: Presents a demo of the solution to the stakeholders.
Scrum Master: Participates in the meeting.
Stakeholders: Give feedback to the developers.
Present the sprint's accomplishments: Show the team's progress and achievements over the past sprint and what has been completed and what has not. To give stakeholders a chance to respond to what was done and provide feedback, the team for software development products may decide to present the completed tasks live or through a presentation.
Review the product backlog: Review the product backlog items that were completed and prioritize the remaining ones based on feedback from the stakeholders. The Scrum Team may decide to specify which Product Backlog items were initially planned for the Sprint and which of those Product Backlog items were completed or not by the end of the Sprint in order to increase transparency.
Receive feedback: Encourage stakeholders to provide feedback on the sprint's results and use this feedback to guide future sprint planning. In this way, transparency is created. Stakeholders can make informed decisions now because they have the necessary information. Generally speaking, it's a good idea to specify the type of feedback you're seeking. That demonstrates the developers' interest in their viewpoint as well, giving your stakeholders a sense of being heard.
Discuss next steps: Discuss the next steps for the team, including what will be done in the next sprint and any roadblocks that need to be addressed. A review of the Product Forecast could follow the Sprint review. The Product Forecast is a forecast of the potential release dates for the upcoming features and functionality.
Reflect on the process: Take time to reflect on the sprint process and identify areas for improvement to ensure future sprints run more smoothly.
