It’s the moment of truth. The Scrum team demonstrates their work from the current sprint to stakeholders for review. In the mix of excitement and fear, you might be wondering…
How do I run an effective sprint review?
The sprint review is a critical moment of feedback and collaboration. Learning to run an effective sprint review will produce significant fruit for your team. This post will introduce you to the why, the who and the how of the sprint review.
The product owner invites everyone and facilitates the session. They present and demonstrate the Scrum team's work to the stakeholders, explaining both the why and what. They explain how the functionality meets business or customer needs.
The rest of the scrum team actively listens to the feedback and reactions. Having the team present lets them see how stakeholders and customers respond to what they created. This feedback and insight can be encouraging and also deliver insights for future work. It’s not uncommon to see something the team thought was common produce extra delight or to see something the team thought was clear create confusion.
Being in the room and seeing people’s actual responses locks this feedback in the team's mind in a way reading the notes from the meetings can’t. This awareness is a crucial reason the whole team attends.
If you’re on the scrum team but not the product owner, try listening like you’re not on the team. Imagine you’re a potential customer selected to attend and give feedback. Are you excited about what they’re presenting? Does it make you want to purchase the product or service?
The development team can also help by answering questions when needed. Stakeholders may be curious if a new feature can also perform a different but related task.
Leaning Scrum for the first time can be a bit overwhelming. There are many new terms and concepts in Scrum.
Well we’re here to help.