Get More from Your Sprint Review

Bart has been in ecommerce for over 20 years, and can't imagine a better job to have. He is interested in all things agile, or anything new to learn.

SHARE
Request to reuse this
Add to my favorites
Topics: Agile, Requirements Management, Stakeholder Management, Teams

One of the most important Agile ceremonies is the Sprint Review. This is typically a live meeting near or at the end of a sprint or every other sprint. Developers, product team members and stakeholders gather to see what was built since the last review. Following the agile goal of working software, the team should be able to show new features and functionality. This part of the review might be called a Sprint Demo.

But the demo is merely a part of the sprint review. In addition, the team should review the goals of the product and how completed work aligns with the project’s overall aims. The team should determine if the work done in the past sprint helped meet the goals or fell short—perhaps the team worked on something great but didn’t make progress towards the goal at all. This is the time when the team can course-correct; perhaps, it will choose different stories for the next sprint, or change focus, or if needed, look to change the resourcing of the team so that different stories can be accomplished in future sprints or to impact the velocity of the team.

The sprint review also helps stakeholders better understand the status of the product and allows them to use and see the product, perhaps for the first time. This can lead to productive discussions about the product, including whether it is ready for customers, what still needs to be built, the release plan, and the …

Please log in or sign up below to read the rest of the article.