CSPO Stakeholder and User Engagement 4 â Questions and Answers
Question 1: A Product Owner uses a 'Buy a Feature' prioritization game with stakeholders. What is the PRIMARY benefit of this technique?
- It allows the Development Team to estimate feature complexity
- It engages stakeholders in prioritization by forcing trade-off decisions with a limited budget (Correct answer)
- It replaces the need for user stories in the Product Backlog
- It enables the Scrum Master to resolve backlog disputes
Correct answer: It engages stakeholders in prioritization by forcing trade-off decisions with a limited budget
'Buy a Feature' forces stakeholders to make real trade-off decisions by allocating a limited budget, revealing true priorities through constraint.
Question 2: What is the role of personas in helping a Product Owner engage with users effectively?
- Personas replace the need for actual user research
- Personas create fictional but data-grounded representations of user segments to guide product decisions (Correct answer)
- Personas are used exclusively during Sprint Retrospectives
- Personas help estimate story points for user stories
Correct answer: Personas create fictional but data-grounded representations of user segments to guide product decisions
Personas are research-based archetypes representing user groups that help the Product Owner and team make user-centered decisions.
Question 3: During Sprint Planning, a stakeholder insists on attending and directing the team's work. How should the Product Owner handle this?
- Welcome the stakeholder and allow them to assign tasks to team members
- Explain that Sprint Planning is a Scrum Team event and offer alternative ways for the stakeholder to provide input (Correct answer)
- Ask the Scrum Master to remove the stakeholder from the organization
- Cancel Sprint Planning and reschedule when the stakeholder is unavailable
Correct answer: Explain that Sprint Planning is a Scrum Team event and offer alternative ways for the stakeholder to provide input
Sprint Planning is a Scrum Team event; the Product Owner should redirect stakeholder involvement to appropriate channels like Product Backlog refinement or Sprint Reviews.
Question 4: A Product Owner wants to validate a new product idea before committing Sprint capacity to it. Which approach is MOST aligned with Scrum values?
- Spend several Sprints building the full feature before testing it with users
- Create a lightweight prototype or experiment to test the assumption with real users quickly (Correct answer)
- Ask the Scrum Master to approve the idea before proceeding
- Wait for a competitor to build it first to see if users want it
Correct answer: Create a lightweight prototype or experiment to test the assumption with real users quickly
Creating lightweight experiments or prototypes allows the Product Owner to validate assumptions quickly and with minimal investment, reducing risk.
Question 5: Which metric is MOST useful for a Product Owner to understand whether users are getting value from the product?
- Number of user stories completed per Sprint
- User engagement metrics such as retention rate, task completion rate, or NPS (Correct answer)
- Number of stakeholder meetings held per month
- Team velocity over the last five Sprints
Correct answer: User engagement metrics such as retention rate, task completion rate, or NPS
Outcome-based metrics like retention, task completion, and NPS directly measure whether users are gaining value, unlike output metrics like velocity.
Question 6: A new regulatory stakeholder joins the project mid-way with compliance requirements. How should the Product Owner respond?
- Ignore regulatory requirements until the product is fully built
- Add regulatory requirements to the Product Backlog and prioritize them based on risk and compliance deadlines (Correct answer)
- Delegate all regulatory concerns to the legal department
- Stop all development until every regulation is addressed
Correct answer: Add regulatory requirements to the Product Backlog and prioritize them based on risk and compliance deadlines
Regulatory requirements are legitimate product needs that should be captured as Product Backlog items and prioritized based on their importance and timing.
Question 7: What does 'co-creation' with users mean in the context of product ownership?
- Allowing users to write their own user stories without Product Owner involvement
- Actively involving users in the design and discovery process to build solutions together (Correct answer)
- Letting users vote on which features developers will build
- Outsourcing product design entirely to an external user group
Correct answer: Actively involving users in the design and discovery process to build solutions together
Co-creation involves actively collaborating with users during discovery and design to ensure solutions are grounded in real needs and context.
A Product Owner uses a 'Buy a Feature' prioritization game with stakeholders.
What is the PRIMARY benefit of this technique?