Certified Scrum Product Owner®(CSPO) Product Assumption Validation 1 Flashcards

A Product Owner wants to validate the assumption that customers will pay a premium price for an advanced analytics dashboard. Which approach provides the MOST reliable signal before building the full feature?

Answer: Create a landing page describing the feature and measure how many users click 'Buy Now' before the feature exists

A fake-door or smoke-test landing page reveals actual purchase intent by measuring real behavior (clicks on a buy button) rather than stated preferences. This is far more reliable than a survey, which captures what people say rather than what they do, and more actionable than estimation or roadmap inclusion.

Which statement BEST describes the difference between a validated assumption and a validated learning in product development?

Answer: A validated assumption confirms a belief before building; a validated learning is insight gained after running an experiment

A validated assumption uses lightweight evidence to confirm or refute a belief prior to committing resources, while validated learning is the broader insight — positive or negative — produced by running a structured experiment. The distinction matters because an assumption can be invalidated, producing equally valuable learning.

A Product Owner maps all assumptions for an upcoming feature and finds one that is both highly uncertain AND would be catastrophic if wrong. According to assumption prioritization frameworks, what should the Product Owner do?

Answer: Validate it immediately, as high uncertainty combined with high impact makes it the riskiest assumption

Assumption prioritization frameworks such as the Risk/Uncertainty matrix direct teams to tackle assumptions that are both highly uncertain and highly consequential first. Deferring such an assumption allows the team to invest heavily in work that may be entirely invalidated, wasting Sprint capacity.

The Product Owner hypothesizes that simplifying the onboarding flow will reduce user drop-off. After one Sprint running a split test, the simplified flow shows only a 1% improvement. What is the MOST appropriate next step?

Answer: Treat the result as a falsified hypothesis, document the learning, and explore alternative explanations for drop-off

A 1% improvement that likely falls within the margin of error means the hypothesis was not confirmed. The correct response is to treat it as a falsified assumption, capture the learning (simplification alone is not the lever), and pivot to investigating other root causes of drop-off rather than reverting blindly or continuing indefinitely.

During backlog refinement, a stakeholder insists that 'everyone knows' users want dark mode, so no validation is needed. How should the Product Owner respond?

Answer: Acknowledge the belief, then propose a lightweight experiment such as a feature-request vote or usability test to surface real evidence before committing Sprint capacity

'Everyone knows' is a classic unvalidated assumption dressed as fact. The Product Owner's responsibility is to maximize value, which means testing assumptions before committing the team's capacity. A lightweight validation step (vote, poll, or prototype test) quickly converts belief into evidence without delaying the roadmap significantly.

A Product Owner is building a mobile app and assumes that push notifications will increase daily active users. Which metric would BEST serve as the success criterion for an experiment validating this assumption?

Answer: Seven-day retention rate of users who opted into notifications versus those who did not

The assumption is that push notifications drive active usage, so the experiment must measure actual usage behavior — specifically retention. Comparing seven-day retention between opted-in and opted-out cohorts directly tests whether notifications cause users to return, isolating the effect of the feature rather than conflating it with downloads or send volume.