Stakeholders & Scaling

How are stakeholders primarily engaged with the Scrum Team during the Sprint cycle?

• A Through the Daily Scrum, which they run
• B Through the Sprint Review, where they collaborate on what to do next ✓
• C Through the Sprint Retrospective
• D They are not engaged at all

Answer: The Sprint Review is the event where the Scrum Team presents results to key stakeholders and collaborates with them on progress toward the Product Goal and what to do next.

When multiple Scrum Teams work on the same product, how many Product Owners and Product Goals should there be?

• A A committee of Product Owners
• B One Product Goal per Sprint per team
• C One Product Owner and one Product Goal for the product ✓
• D One Product Owner per team, each with its own goal

Answer: If multiple teams work on one product, they should share one Product Owner, one Product Backlog and one Product Goal, keeping a single source of direction and value.

A Product Owner is overwhelmed by conflicting demands from many stakeholders. Which response best fits the Product Owner accountability?

• A Create a separate Product Backlog for each stakeholder
• B Hand all decisions to the Scrum Master
• C Implement every request in the order received
• D Make value-based ordering decisions on a single Product Backlog and clearly communicate the rationale ✓

Answer: The Product Owner represents many stakeholders' needs through one ordered Product Backlog, making transparent value-based decisions rather than fragmenting the backlog or deferring the accountability.

What is the most appropriate way for a Product Owner to keep stakeholders informed of product direction?

• A Maintain a transparent Product Backlog and a clearly communicated Product Goal that stakeholders can see and understand ✓
• B Send velocity charts only to managers
• C Rely on the Scrum Master to brief stakeholders privately
• D Keep the Product Backlog hidden to avoid confusion

Answer: Transparency is a Scrum pillar; the Product Owner ensures the Product Backlog is visible and understood and communicates the Product Goal so stakeholders share an accurate view of direction.

Several teams on one product each maintain their own separate backlog and priorities. From a scaling perspective, what is the main risk?

• A Loss of a single source of truth and conflicting priorities that obscure overall product value ✓
• B The Scrum Master cannot run the Daily Scrum
• C Velocity becomes too high
• D None; separate backlogs are recommended when scaling

Answer: Scaling Scrum keeps one Product Backlog and one Product Goal per product; separate backlogs fracture transparency and create conflicting priorities that make overall value hard to manage.

During a Sprint Review, stakeholders suggest several new ideas. What is the correct outcome?

• A The Sprint Review is a working session; the Product Owner considers the input and may adapt the Product Backlog accordingly ✓
• B The Scrum Master decides which ideas to accept
• C Stakeholder ideas must be ignored to protect the plan
• D The ideas are automatically added to the next Sprint

Answer: The Sprint Review is a collaborative working session, not a one-way demo; the attendees discuss what to do next and the Product Owner adapts the Product Backlog based on the input received.