CSPO Stakeholder Engagement 4 — Questions and Answers
Question 1: A newly appointed Product Owner inherits a product with no clear stakeholder map. What should they do first?
- Immediately begin refining the Product Backlog
- Identify all stakeholders, understand their interests and influence, and establish communication channels (Correct answer)
- Cancel the next Sprint to gather requirements
- Ask the Scrum Master to handle stakeholder communication
Correct answer: Identify all stakeholders, understand their interests and influence, and establish communication channels
Understanding the stakeholder landscape is foundational for a PO to effectively represent needs and manage relationships.
Question 2: How should a Product Owner handle a stakeholder who keeps reopening decisions that have already been made?
- Ignore the stakeholder's input going forward
- Revisit every decision to keep the stakeholder happy
- Acknowledge their concern, explain the rationale behind the decision, and reference empirical outcomes (Correct answer)
- Escalate to senior management immediately
Correct answer: Acknowledge their concern, explain the rationale behind the decision, and reference empirical outcomes
Grounding decisions in transparent reasoning and empirical data helps stakeholders accept outcomes even when they disagree.
Question 3: What is the most effective way for a Product Owner to communicate a significant change in product direction to stakeholders?
- Send a single mass email announcement
- Update the Product Backlog silently and let stakeholders discover changes in the next Sprint Review
- Proactively engage stakeholders, explain the rationale, and address their concerns directly (Correct answer)
- Ask the Scrum Master to announce the change in the next team meeting
Correct answer: Proactively engage stakeholders, explain the rationale, and address their concerns directly
Proactive, transparent communication with clear rationale maintains stakeholder trust during periods of change.
Question 4: During a Sprint Review, a stakeholder says the feature delivered is not what they envisioned. What does this indicate?
- The team did not work hard enough
- The Sprint Review is working as intended — this feedback will inform the next iteration (Correct answer)
- The Definition of Done was not followed
- The Scrum Master failed to communicate properly
Correct answer: The Sprint Review is working as intended — this feedback will inform the next iteration
Sprint Reviews are designed to surface exactly this kind of feedback so the product can be adapted — this is empiricism working correctly.
Question 5: A stakeholder insists on detailed up-front requirements before the first Sprint. How should the PO respond?
- Agree and spend several weeks gathering all requirements before starting
- Explain that Scrum embraces uncertainty and that requirements evolve through iterative delivery and feedback (Correct answer)
- Refuse to engage with the stakeholder's concerns
- Revert to a waterfall approach to satisfy the stakeholder
Correct answer: Explain that Scrum embraces uncertainty and that requirements evolve through iterative delivery and feedback
The PO should educate stakeholders on the empirical nature of Scrum and why iterative delivery produces better outcomes than exhaustive upfront planning.
Question 6: What role does the Product Owner play in managing stakeholder expectations about the product roadmap?
- The PO should never share roadmap information to avoid commitment
- The PO sets realistic expectations by sharing a transparent, adaptable roadmap and explaining its probabilistic nature (Correct answer)
- The PO delegates roadmap communication entirely to the Scrum Master
- The PO should commit to fixed roadmap dates to build confidence
Correct answer: The PO sets realistic expectations by sharing a transparent, adaptable roadmap and explaining its probabilistic nature
A good PO shares a transparent roadmap while helping stakeholders understand it will adapt based on learning and changing conditions.
Question 7: Which action best demonstrates effective stakeholder collaboration in a Scrum context?
- Conducting a one-time stakeholder survey at project kickoff
- Co-creating the Product Goal with key stakeholders and revisiting it regularly (Correct answer)
- Limiting stakeholder input to formal governance checkpoints
- Allowing stakeholders to directly assign tasks to developers
Correct answer: Co-creating the Product Goal with key stakeholders and revisiting it regularly
Co-creating the Product Goal ensures stakeholder alignment from the start and promotes ongoing collaboration around shared purpose.
CSPO Stakeholder Engagement 4
A newly appointed Product Owner inherits a product with no clear stakeholder map.
What should they do first?