CSPO - Certified Scrum Product Owner® Certification Certified Scrum Product Owner®(CSPO) Stakeholder Engagement 1 — Questions and Answers
Question 1: A Product Owner discovers that a major stakeholder group—end users—has never been invited to Sprint Reviews. What is the MOST important reason to include them going forward?
- To satisfy the Scrum Guide's mandatory attendance requirement for all stakeholder types
- To gather direct feedback on delivered increments and validate that the product solves real user problems (Correct answer)
- To give the Development Team an opportunity to demonstrate technical achievements
- To reduce the Product Owner's workload by letting users prioritize the backlog directly
Correct answer: To gather direct feedback on delivered increments and validate that the product solves real user problems
End users are the people whose problems the product must solve. Their direct feedback during Sprint Reviews provides the most authentic signal about whether the increment delivers real value, which is the core purpose of the event.
Question 2: A Product Owner is working with a geographically distributed stakeholder group spanning multiple time zones. Sprint Reviews are difficult to schedule. What is the BEST approach?
- Cancel formal Sprint Reviews and rely solely on email updates to stakeholders
- Record the Sprint Review and send stakeholders a link, replacing all live interaction
- Hold multiple shorter review sessions at different times and supplement with async artifacts like demo videos and written summaries (Correct answer)
- Require all stakeholders to attend a single session at the time most convenient for the Product Owner
Correct answer: Hold multiple shorter review sessions at different times and supplement with async artifacts like demo videos and written summaries
Distributed stakeholder groups require flexible engagement strategies. Multiple sessions combined with async artifacts ensure broad participation and timely feedback without excluding anyone due to time zone barriers.
Question 3: During Product Backlog refinement, a stakeholder requests detailed specifications for every item, including those far down the backlog. How should the Product Owner respond?
- Provide detailed specifications for all items to maintain full stakeholder transparency
- Explain that only items near the top of the backlog need sufficient detail for upcoming Sprints, and that lower-priority items will be refined closer to implementation (Correct answer)
- Ask the Development Team to write the specifications so the stakeholder is satisfied
- Remove low-priority items from the backlog to avoid the stakeholder's request
Correct answer: Explain that only items near the top of the backlog need sufficient detail for upcoming Sprints, and that lower-priority items will be refined closer to implementation
Progressive elaboration is a core backlog management principle. Over-specifying low-priority items wastes effort since requirements often change before those items are ever developed. The Product Owner should explain this trade-off to stakeholders.
Question 4: A Product Owner receives contradictory feedback: the sales team wants a pricing calculator feature urgently, while customer support data shows users most frequently struggle with the onboarding flow. How should the Product Owner decide what to prioritize?
- Always prioritize the sales team because they directly generate revenue
- Prioritize based on a combination of user impact data, business value, and strategic alignment—using the support data as strong evidence for the onboarding fix (Correct answer)
- Flip a coin since both stakeholder groups are internal and equally valid
- Let the Scrum Master break the tie since the Product Owner is too close to the decision
Correct answer: Prioritize based on a combination of user impact data, business value, and strategic alignment—using the support data as strong evidence for the onboarding fix
Effective prioritization balances multiple inputs: quantitative user data (support tickets), business impact, and strategic goals. Empirical evidence from customer support data is particularly valuable because it reflects actual user pain points at scale.
Question 5: A stakeholder asks the Product Owner to commit to delivering a specific set of features by a hard deadline six months away. What is the MOST appropriate response?
- Agree to the commitment immediately to maintain the stakeholder relationship
- Explain that in Scrum, long-range feature commitments undermine empirical planning, but offer to share the current roadmap priorities and revisit the conversation each Sprint (Correct answer)
- Tell the stakeholder that only the Scrum Master can make delivery commitments
- Refuse any discussion of timelines, citing agile principles forbidding estimates
Correct answer: Explain that in Scrum, long-range feature commitments undermine empirical planning, but offer to share the current roadmap priorities and revisit the conversation each Sprint
Product Owners must balance stakeholder expectations with Scrum's empirical nature. Rather than making a binding commitment that could become a false promise, the PO provides current best-known priorities and a cadence for regular updates as the team learns more.
Question 6: A Product Owner notices that one influential stakeholder consistently dominates Sprint Review discussions, causing other stakeholders to disengage. What should the Product Owner do?
- Remove the dominant stakeholder from future Sprint Reviews to restore balance
- Accept the dynamic since the most influential stakeholder's feedback is most important
- Facilitate the Review more actively by explicitly inviting quieter stakeholders to share their perspectives and setting discussion norms at the start of the session (Correct answer)
- Ask the Scrum Master to manage the dominant stakeholder privately before the session
Correct answer: Facilitate the Review more actively by explicitly inviting quieter stakeholders to share their perspectives and setting discussion norms at the start of the session
The Product Owner is responsible for ensuring Sprint Reviews yield diverse, actionable feedback. Active facilitation—such as structured turn-taking, direct invitations to quieter voices, and setting expectations upfront—creates an environment where all stakeholders can contribute meaningfully.
A Product Owner discovers that a major stakeholder group—end users—has never been invited to Sprint Reviews.
What is the MOST important reason to include them going forward?