CSPO Understanding Customers and Users 5 â Questions and Answers
Question 1: A Product Owner is preparing for a Sprint Review and wants to include customer feedback. Which approach provides the most direct customer insight?
- Summarizing internal team assumptions about user needs
- Inviting actual customers or users to participate in the review (Correct answer)
- Reading app store ratings aloud to stakeholders
- Sharing a list of upcoming feature requests
Correct answer: Inviting actual customers or users to participate in the review
Direct customer participation in Sprint Reviews provides real-time, firsthand feedback that is more actionable than secondhand summaries.
Question 2: A Product Owner notices that users frequently use a feature in an unexpected way. What should the Product Owner do?
- Restrict the unintended use through technical controls
- Investigate why users behave this way and consider whether the product design needs adjustment (Correct answer)
- Add it to the 'known issues' list and ignore it
- Rewrite the user manual to correct user behavior
Correct answer: Investigate why users behave this way and consider whether the product design needs adjustment
Unexpected usage patterns often reveal unmet needs or design gaps that represent valuable product improvement opportunities.
Question 3: What is the difference between 'user needs' and 'user wants' in the context of product ownership?
- They are identical terms used interchangeably in Scrum
- Needs are underlying goals users must achieve; wants are specific solutions users think will achieve them (Correct answer)
- Wants are higher priority than needs in the Product Backlog
- Needs are documented in the Sprint Goal; wants go in the backlog
Correct answer: Needs are underlying goals users must achieve; wants are specific solutions users think will achieve them
Distinguishing needs from wants allows the Product Owner to explore better solutions rather than simply building what users explicitly requested.
Question 4: How does continuous delivery of working software help a Product Owner better understand customers?
- It eliminates the need for user research entirely
- Frequent releases generate real usage data and feedback that inform the next iteration (Correct answer)
- It allows the team to skip sprint reviews
- It guarantees customer satisfaction automatically
Correct answer: Frequent releases generate real usage data and feedback that inform the next iteration
Getting software into users' hands frequently provides empirical feedback about what's working and what isn't, enabling evidence-based decisions.
Question 5: A Product Owner is working on a product used by both novice and expert users. What is the best approach to address both segments?
- Build only for experts since they provide the most feedback
- Research both segments and find solutions that serve each without degrading the other's experience (Correct answer)
- Build two completely separate products
- Prioritize novice users and ignore expert needs
Correct answer: Research both segments and find solutions that serve each without degrading the other's experience
Understanding each segment's distinct needs allows the Product Owner to make informed decisions about how to balance the product experience for different user types.
Question 6: What role does the 'voice of the customer' play in Product Backlog refinement?
- It is used only to write the Definition of Done
- It helps the Product Owner explain the 'why' behind backlog items, ensuring the team understands user context (Correct answer)
- It replaces the need for acceptance criteria
- It is presented only at the end of the project
Correct answer: It helps the Product Owner explain the 'why' behind backlog items, ensuring the team understands user context
Sharing customer context during refinement helps the development team make better technical decisions aligned with actual user needs.
Question 7: A Product Owner finds that churn rate is rising despite positive survey scores. What is the most likely explanation?
- The development team is too slow
- Surveys measure stated satisfaction while churn reflects actual behavior â users may leave for reasons they don't articulate in surveys (Correct answer)
- The Scrum Master is not running retrospectives correctly
- The product backlog is too long
Correct answer: Surveys measure stated satisfaction while churn reflects actual behavior â users may leave for reasons they don't articulate in surveys
Survey data captures what users say, not what they do; behavioral metrics like churn often reveal unspoken dissatisfaction or unmet needs.
CSPO Understanding Customers and Users 5
A Product Owner is preparing for a Sprint Review and wants to include customer feedback.
Which approach provides the most direct customer insight?