CSPO Stakeholder Engagement 5 â Questions and Answers
Question 1: A stakeholder group wants monthly in-depth progress reports. The Product Owner believes this adds little value. What is the best approach?
- Refuse to provide reports and redirect them to Sprint Reviews
- Understand their underlying need and explore whether the Sprint Review cadence can address it (Correct answer)
- Assign report creation to the development team
- Create monthly reports to avoid conflict
Correct answer: Understand their underlying need and explore whether the Sprint Review cadence can address it
Understanding the stakeholder's underlying need may reveal that existing Scrum events can meet it without creating wasteful reporting overhead.
Question 2: Why is it important for the Product Owner to manage stakeholder expectations about technical debt?
- Technical debt is a purely internal concern and should never be shared with stakeholders
- Unmanaged technical debt slows delivery and affects quality, so stakeholders need to understand the trade-offs (Correct answer)
- Stakeholders should always be shielded from technical concerns
- Only the Scrum Master needs to understand technical debt implications
Correct answer: Unmanaged technical debt slows delivery and affects quality, so stakeholders need to understand the trade-offs
Educating stakeholders about technical debt empowers them to make informed decisions about trade-offs between speed and long-term product health.
Question 3: A high-influence stakeholder requests a feature that would benefit only a small user segment. What should the Product Owner do?
- Immediately prioritize it due to the stakeholder's seniority
- Evaluate the feature's overall value, its impact on the broader user base, and weigh it against competing priorities (Correct answer)
- Decline the request without discussion
- Add it to the backlog and de-prioritize it without explanation
Correct answer: Evaluate the feature's overall value, its impact on the broader user base, and weigh it against competing priorities
POs must evaluate all requests based on value to the broader product and user base, not stakeholder seniority alone.
Question 4: What is the most critical factor that distinguishes effective stakeholder engagement from mere stakeholder management?
- Sending frequent status updates
- Building genuine two-way communication that incorporates stakeholder feedback into product decisions (Correct answer)
- Maintaining a formal RACI matrix
- Limiting stakeholder access to protect the team's focus
Correct answer: Building genuine two-way communication that incorporates stakeholder feedback into product decisions
Effective engagement is bidirectional â it means actually incorporating stakeholder input into decisions, not just keeping them informed.
Question 5: Which scenario represents a Product Owner violating good stakeholder engagement principles?
- Inviting a key customer to the Sprint Review
- Making Product Backlog decisions in private to avoid conflict (Correct answer)
- Explaining the rationale behind a priority decision to a disappointed stakeholder
- Scheduling a pre-Sprint Review with stakeholders to set context
Correct answer: Making Product Backlog decisions in private to avoid conflict
Making Product Backlog decisions in private undermines transparency and collaboration, which are core Scrum values.
Question 6: A Product Owner is working on a B2B product. Which stakeholder typically provides the most valuable product feedback?
- The executive sponsor who funded the project
- The end users who interact with the product daily (Correct answer)
- The legal team responsible for compliance
- The IT department managing the infrastructure
Correct answer: The end users who interact with the product daily
End users provide direct, experiential feedback about usability and value, making their input most critical for product improvement.
Question 7: How does the Scrum value of 'Openness' specifically apply to stakeholder engagement?
- It means sharing only positive progress updates to maintain morale
- It means being transparent about impediments, risks, and trade-offs even when the news is difficult (Correct answer)
- It means allowing stakeholders to attend all internal Scrum events
- It means sharing all internal team communications with stakeholders
Correct answer: It means being transparent about impediments, risks, and trade-offs even when the news is difficult
Openness in Scrum means honestly communicating the real state of the product including challenges, so stakeholders can make informed decisions.
A stakeholder group wants monthly in-depth progress reports.
The Product Owner believes this adds little value.
What is the best approach?