Scribd
Upload
75 views

Sprint Review

The Sprint Review is a meeting at the end of the Sprint where the Scrum Team presents the completed work to stakeholders and gathers feedback to improve upcoming Sprints; it involves demonstrating the working product increment, reviewing outcomes, updating the backlog, and planning next steps.

Uploaded by

venu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
75 views

Sprint Review

The Sprint Review is a meeting at the end of the Sprint where the Scrum Team presents the completed work to stakeholders and gathers feedback to improve upcoming Sprints; it involves demonstrating the working product increment, reviewing outcomes, updating the backlog, and planning next steps.

Uploaded by

venu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Sprint Review

What is the purpose of the Sprint Review?

The purpose of the Sprint Review, from my perspective, is to inspect the outcomes
of the Sprint and decide on necessary adjustments. It's a chance for us to focus on
the product we've been working on, rather than the process. We review and update
the product backlog based on feedback and look for new opportunities that may have
emerged. It's also the time to wrap up the Sprint's work.

Who all attend the Sprint Review?

The Sprint Review meeting includes the Product Owner, the Scrum Master, and the
Scrum Team as core participants. We also involve stakeholders to provide a broader
perspective, and sometimes customers and end users join in, although their
attendance is optional.

How long does the Sprint Review last?

The duration of the Sprint Review is tailored to the length of the Sprint. For
instance, a one-week Sprint would have a review lasting about an hour, while a two-
week Sprint would have a two-hour review. This ensures we have enough time to
thoroughly discuss everything without feeling rushed.

What is the agenda of the Sprint Review?

The agenda starts with the Scrum Master handling introductions, especially if we
have new team members, and setting the expectations. The Product Owner then reviews
the product goal. The Scrum Team presents the working software developed during the
Sprint. Stakeholders provide feedback on the value delivered, and we discuss any
assistance they might offer. The Product Owner talks about what comes next, and we
conclude with a celebration of our achievements and the meeting's closure.

How to provide input during the Sprint Review?

Input during the Sprint Review can be provided through various means, such as Post-
its or sticky notes on platforms like Mural or Miro, a simple document for tracking
feedback, updating the Product Backlog, or utilizing online documentation tools
like TFS Wiki or Confluence.

Who leads the Sprint Review?

The Sprint Review is usually led by a member of the Scrum Team, which could be the
Product Owner or another team member, with the Scrum Master serving as the
facilitator. This ensures that the review process is collaborative and inclusive.

What should we prepare for the Sprint Review?

In preparation for the Sprint Review, the Product Owner should identify the
necessary stakeholders for the review. We make sure that the user stories meet our
definition of done. Together, the Product Owner and the Scrum Team decide what will
be presented, ensuring that we only show work that is relevant and completed.

What happens in a Sprint Review?

During the Sprint Review, we summarize the Sprint's work, inspect the product
increment, and engage in discussions to adapt and improve going forward. The output
includes accepted Product Backlog items, noted feedback, new items added to the
Product Backlog, re-prioritized backlogs, and a Product Backlog that's ready for
the next Sprint.

You might also like