Certified Scrum Product Owner®(CSPO) Stakeholder Engagement 1 Flashcards

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?

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.

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?

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.

During Product Backlog refinement, a stakeholder requests detailed specifications for every item, including those far down the backlog. How should the Product Owner respond?

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.

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?

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.

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?

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.

A Product Owner notices that one influential stakeholder consistently dominates Sprint Review discussions, causing other stakeholders to disengage. What should the Product Owner do?

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.