The sole purpose of Sprint Review is to gather proper feedback on the product delivered and evaluate the collaborations. It is used for inspection of developed increment and also for demonstration. The Sprint Review shows the real working product to the customers.
The stakeholders blend unmistakably into the Scrum teams, making themselves barely recognizable in a big group of people. During the Sprint Review, every developer makes a note of the feedback they have received on their product. For every successful Scrum team, continuous research to gather feedback is crucial. The ideal Sprint Review will only end when all the possible improvements based on the feedback are done.
On the flip side, due to an influx of the participants, the Sprint Review sometimes turns out to be a failure. The Sprint Review in such cases, becomes more like a demo session. Having an overabundance of stakeholders acts as a disadvantage for the Sprint Review. When there is a lack of feedback provided to the developers, they show less interest to attend the Sprint Review. The product owner and the Scrum Master becomes the connecting link between the development team and Stakeholders. This results in a lack of communication between the stakeholders and development team.
Here are the three ideas which help improve Scaled Sprint Review-
# 1 – Arranging a monthly demo besides the regular bi-weekly Sprint review
The primary role of a Sprint Review is to gather feedback, while the demo creates an alignment between everyone interested and involved in the Sprint Review. The demo is very valuable and has different goals as compared to the Sprint Review. Arranging a demo on a monthly basis along with the bi-weekly Sprint Review as per the value stream, may help in gathering the detailed feedback.
# 2 – Dividing the Sprint Review into two parts
Each team uses the first part of their Sprint Review to get a detailed feedback on the “small circle” of acceptors/mandated users. A small circle is usually a group of 4 to 6 people who work closely for both backlog and full cycle engagement. The other section of the team proceeds to join the “large circle” where they have face-to-face contact with all the Scrum Teams in every 6 weeks.
# 3 – Continuous flow acceptance from Sprint Review
By following this technique, all the end-users can be held closely. The Project Owners rely on the team and also the end-users. Engaging with a wider stakeholder community and reconfirming the roadmap with the stakeholders is the agenda. This technique helps to get detailed feedback from Sprint Review, which in the long run helps your scaled teams.
So by understanding the challenges in the Sprint Review and confronting them with the correct solutions, one can achieve the desired goal. You will also learn to organize the Sprint Review according to the increasing team volume and the stakeholders.