In this piece, we’re taking a deep dive into the Sprint Review so that you can learn how to improve the Sprint Reviews in your teams. If you want to learn about the other 4 ceremonies in the Scrum project management system, be sure to check out our blog post on the topic.
Table of Contents
- What is the purpose of the Sprint Review?
- What Sprints Review Are NOT
- How to Conduct Better Sprint Reviews
What is the purpose of the Sprint Review?
Although the Sprint Review embodies all 3 Pillars of Scrum – Transparency, Inspection, and Adaptation – it emphasizes the last two: Inspection and Adaptation. According to the official Scrum Guide, the purpose of a Sprint Review is, “to inspect the outcome of the Sprint and determine future adaptations.”
In other words, you take stock of what was accomplished in the last Sprint and use that to update your plans for future Sprints.
What Sprint Reviews Are NOT
Let’s take a moment to dispel two common misconceptions about Sprint Reviews.
A Sprint Review is NOT just a demo.
A key part of a Sprint Review is that the team presents what they achieved in the last Sprint. This information sharing allows all the relevant stakeholders to be informed about changes to the product. It also helps boost team morale, which we’ll talk about later.
But, a Sprint Review should not just be a string of “show and tells.” Each demo should serve as the launch point for conversation about the new functionality. There should be praise but also questions and feedback about the potentially shippable product increment. Feedback from stakeholders from the business side helps to ensure that product increments are adding the greatest amount of business value.
The Product Owner (who is typically the Product Manager) should take in all this feedback and use it to guide the direction of the product. After the Sprint Review, the Product Owner should have a lot of information to process. The end result should be a Product Backlog that incorporates all the learnings discovered during the Sprint and the Sprint Review.
A Sprint Review is NOT the same thing as a Sprint Retrospective.
This is a super common mistake, and it’s understandable. Both occur after the Sprint and the terms themselves are very similar – what’s the difference between a “review” and “retrospective”?
But the Sprint Review and Sprint Retrospective are completely separate ceremonies. The easiest way to distinguish them is the following: The Sprint Review focuses on the product while the Sprint Retrospective focuses on the process.
In a Sprint Review meeting, every relevant stakeholder is invited, even those who aren’t part of the Scrum team. This is because the focus is on the product. But in a Sprint Retrospective, only the Scrum team is there, because it’s a meeting for the Scrum team about the Scrum team. The goal of the Review is to improve the product in future Sprints while the goal of the Retrospective is to improve how the team performs in future Sprints.
How to Conduct Better Sprint Reviews
Begin by Framing the Sprint Review
At the beginning of every Sprint Review, the Product Owner should remind everyone of the Sprint Goals and give the necessary context to understand the stakes of the Sprint. This helps everyone understand what was intended for the Sprint, why those intentions were set in the first place, and how the outcomes of the Sprint line up with what was planned.
The Sprint Backlog alone can’t answer these questions. That’s why teams rely upon tools like the Project Delivery Tracker from LinearB, which can give them more visibility into the Sprint. LinearB’s Planning Accuracy metric, for instance, tells you at a glance precisely how much of the planned work you actually completed during the Sprint.
Celebrate the Wins
The best teams ensure that Sprint Reviews are celebratory. (There’s a reason many teams hold them on Friday afternoons, right around happy hour.) People worked hard to create new functionality, and that hard work deserves to be recognized. By celebrating one another’s achievements, you bring a team closer together and motivate people for the next Sprint.
Motivating a team is a key part of people management, which is essential to software engineering. On the Dev Interrupted Podcast, Hyrum Wright, Senior Staff Engineer at Google, explained how he believes that software engineering is not a technical problem but a people problem.
If your team comes out of a Sprint Review not feeling excited for the next Sprint, this indicates something is wrong. A common cause is that teams feel like they’ve let the company down when they don’t meet their Sprint Goals.
LinearB can help you prevent this disappointment. The Investment Profile metric tells you exactly where the development team spent their time during the Sprint. This enables you to identify and easily communicate what the team did accomplish. For example, they may have had to respond to urgent bug fixes or pay down technical debt that prevented them from shipping new functionality. But that work was valuable and it deserves to be celebrated even if it wasn’t planned for.
Take the Time to Update the Product Backlog
Once the Sprint Review is over, the Product Owner should process all the feedback, extracting insights and action items. All this new information should make its way into the Product Backlog. The Product Owner should add new user stories and issues as well as update the data on existing Product Backlog items like their business value and story points. This ensures that the next Sprint Planning session is more constructive and that the upcoming Sprint will be more fruitful.
LinearB can make the process of updating the backlog not only faster but also more accurate. The Pulse Dashboard shows you how much work went into each issue, so that you can see whether you are systemically misestimating how much work an issue/user story requires. The Planning Accuracy metric can also help reveal if there’s a persistent mismatch between work anticipated and work required. By having a better grasp of achievable delivery dates, you can plan better and improve alignment across the entire company.
Just because the development work has finished, a Sprint isn’t over. You need to also bring energy and intentionality to the Sprint Review.
It will help to replenish enthusiasm among the team heading into the next Sprint. A high-quality Sprint Review also helps to inform everyone about how the product has changed and give them the opportunity to share feedback and ensure that the product is heading in the right direction. This means that the hard work done during future Sprints will prove to be even more valuable.
With LinearB you can not only have more productive Sprint Reviews but also improve each stage of your development process. Get in touch with us to set up a demo and learn about all the ways you can start shipping better code faster with LinearB.