Mike Lyons walks through the Sprint Review, the Scrum ceremony where teams show finished work to the Product Owner and stakeholders, collect feedback, and plan next steps. The review focuses on completed and incomplete backlog items, not status reports.
So the Sprint review. This is another one of our ceremonies in the Scrum 353. It's an exciting event. It occurs at the end of the Sprint. It's really the second to last ceremony you're going to have in your Sprint, but it's our time to shine. It's the team's time to demonstrate all of the hard work that they've done not only to their product owner, but also to stakeholders. It's a wonderful opportunity to show off that hard work that we've been doing together. We used to call it the Sprint demo. We've changed that language a bit. We call it a Sprint review now because we do more than just demo the software. So there are some key components of this event, including the team demonstrates working pieces of value to the customer and stakeholders. Our primary focus is on receiving feedback on the product and then we collaborate on what to do next. Now this is not a status meeting. This is a time to review actual progress of working solutions, which should remind us of the Agile Manifesto principle. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. So, so at the review we're gathering that feedback and potentially creating new backlog items that we can put in the backlog for prioritization for future work. Of course the product owner attends this. The Scrum Master is facilitating it. The whole team is there. I love it when the product owner actually does the demo because it's their product, let them do the demo. But we also don't want to take that opportunity away from developers. Maybe they want a demo. That's awesome too. Our customers are there. Other stakeholders are in this event and we want to time box this event typically one to two hours with a preference towards the one hour time slot. Now some guidelines for a better Sprint review. Some things to consider. Product owners discuss the current state of the product backlog and updating the product backlog as needed. Team members are focused on demonstrating the working software, collaborating with the group to gain feedback and referring to backlog items that weren't completed. So not only do we demo the work that we completed, we also talk about the work we didn't complete. Agile is all about empirical data and full transparency. So let's describe what we didn't get completed and and why. And it's okay, we need to make that visible. And then finally, of course, our Scrum Master. Now our Scrum Master is facilitating the event, ensuring the discussions are focused on feedback, they're helping with collaboration and making sure that we have everything needed to demonstrate the functionality that we've completed as a team. The Sprint review, a great chance for you to shine as a team.
