The Sprint Review Symphony: Orchestrating the Perfect Attendance

Welcome to an essential discussion on the sprint review, a pivotal event in the scrum framework. But who should be present at this significant gathering, and why does their attendance matter? 

The sprint review isn't just about showcasing progress; it's a collaborative space where the product's current state is assessed, and the future direction is charted. The people in the room play a crucial role in these processes. 

In this post, we'll delve into the composition of the sprint review attendees and explore why selecting the right stakeholders is key to clearly understanding where the product stands and making informed decisions about the next steps. Together, we'll unveil the significance of orchestrating the perfect attendance for a successful sprint review.

Further reading: Sample Sprint Review Agenda

The Purpose of the Sprint Review

The sprint review serves two essential functions:

• Understanding the Current Situation: Assessing the product's standing concerning the defined product goal.
• Deciding the Future Direction: This part involves a collective decision about the next steps. Based on the current status, what actions should be taken to continue moving toward the product goal?

Yes, we can also collect feedback from all stakeholders, including the team, but it's far better to collect that feedback during the sprint through interaction between the stakeholders and the developers than to wait until the sprint review for all of the “hey, wait, I forgot this…”-type surprises.

For instance, if the product goal is to enhance response across all features by 25%, and the sprint review reveals that some features have been improved by 10%, we use the sprint review to decide what we should attack next. Should we go from 10% to 15% with the features the team worked on in the previous sprint, or should we try for 10% on other features? And if so, which features?

Who Should Attend the Sprint Review?

The right stakeholders' attendance ensures a complete understanding of progress and an informed decision about the next steps.

• Selecting the Right Stakeholders: Include those who have a direct interest or influence on the product goal, such as subject matter experts and stakeholders with a vested interest in the aspects of the product that are under development. Some of the stakeholders you might want to consider include:
• Sales and Marketing Representatives: They can provide insights into market demands and customer feedback.
• Customer Support Representatives: Individuals who directly interact with users and can share user experiences and concerns.
• Customers or End Users: Those who use or will use the product offer first-hand feedback and insights.
• Suppliers or Vendors: Their perspective on integration and alignment might be valuable if they provide essential components or services.
• Investors: Those interested in the product's success and wanting to understand how the development aligns with broader business goals.
• Regulatory Compliance Officers: If the product must meet specific regulations, having a representative ensures alignment with legal requirements.
• Industry Experts or Consultants: Specialists who can offer unique insights, perspectives, or validation on the product's direction.
• Partners and Collaborators: External organizations or individuals working closely with the development team on the product.
• Adjusting Over Time: As the development evolves, reassess who should attend to ensure the sprint review remains effective. Stakeholder attendance at sprint reviews isn't static; it evolves as the development effort progresses and the product matures. Several factors might drive the change in attendance, and having the right people at the right time can make all the difference. Here are some examples of how stakeholder attendance might have to change over time:
• Early Stages of Development: In the beginning, you may need more involvement from technical experts, business analysts, and those responsible for setting the initial requirements. As the product takes shape, the attendance of these stakeholders may become less frequent.
• Midway Through Development: As the product evolves, you may need to involve marketing and sales representatives, or potential customers, to assess how well the product aligns with market demands or user needs.
• Approaching a Major Release: Close to a major launch, quality assurance, regulatory compliance officers, and customer support representatives might become vital attendees. Their insights ensure the product meets quality standards and is prepared for the market.
• Post-Release Phases: After a product has been released, you should involve actual users, customer support, and maintenance teams to gather feedback, understand the user experience, and plan for improvements or additional features.
• Shifting Business Goals: If the company's strategic goals or market conditions change, the stakeholder composition may need to include those who can guide the product in the new direction, such as new business partners, investors, or industry consultants.
• Regulatory Changes: If new regulations come into play, the attendance of legal or compliance experts might be required to ensure alignment with the legal framework.
• Scaling or Downsizing Efforts: If the development effort is scaled up or down, you might need to include or exclude certain stakeholders to match the new scope and resources.
• Responding to Customer Feedback: If the sprint reviews reveal consistent customer feedback or demands, you may want to increase the involvement of those specific customers or market segments to tailor the product more closely to their needs.

Stakeholders' Role in the Sprint Review

The sprint review is a symphony, and every stakeholder plays an essential part. Here's how:

• Development Team Members: They present the work completed during the sprint, sharing insights, challenges, and successes. Their hands-on experience with the product offers a technical perspective.
• Product Owner: Guides the review, clarifies the product goal, and ensures the conversation stays aligned with the product's vision and roadmap.
• Scrum Master: Facilitates the meeting, encourages collaboration, and ensures everyone understands their review roles.
• Customers or End Users: Offer invaluable feedback from a user's perspective, and share their experiences, needs, and desires.
• Business Analysts and Sales/Marketing Representatives: Assess how well the product aligns with market and business needs. They can provide insights into customer demands and trends.
• Quality Assurance Team: Share the results related to product quality and adherence to standards, and propose areas for improvement.
• Regulatory Compliance Officers: Ensure that the product meets the legal and regulatory standards, offering guidance on compliance matters.
• Investors and Partners: Offer a broader business perspective and assess how the development aligns with the company's overall strategy and goals.
• Industry Experts or Consultants: Provide an external view, offering validation, insights, or unique perspectives on the product's direction.
• Suppliers or Vendors: Offer insights into integration and alignment with external components or services, facilitating seamless collaboration.

The diversity of roles ensures a multifaceted view of the product, fostering a shared understanding and collaboration. Each stakeholder's participation contributes to a robust discussion, leading to informed decisions on the product's future direction.

Remember, orchestrating the perfect attendance isn't about inviting everyone but about having the right people to play these essential roles at the right time.

Collaborating Toward a Common Goal

The sprint review is a living collaboration, a stage where everyone involved in a product's journey comes together to understand, reflect, and decide. Everyone plays a unique and indispensable part in this ongoing adventure, from the team members to the stakeholders. Selecting the right attendees for the sprint review isn't just about filling seats with the same people sprint after sprint; it's about orchestrating a meeting of the right minds, all aimed at one common goal.

Imagine standing at a crossroads, the product goal on the horizon and the path filled with possibilities. The sprint review is where we gather around, map in hand, compass at the ready, deciding our next move. By ensuring that the right stakeholders are present, we have a richer understanding of where we stand and gain the collective wisdom to choose the best path forward.

The product goal, such as improving product response across all features by 25%, is the North Star guiding us. The findings in sprint reviews, like discovering 10% improvement in some features, are milestones marking our progress. Together, they inform our decisions and inspire our next steps.

So, as you set up your next sprint review, remember, it's not just about ticking off a checklist; it's about creating a space where insights are shared, progress is celebrated, decisions are made, and the product's future is shaped with clarity and confidence.

Ready for more tips and agile resources delivered to your inbox? Please subscribe to our emails!