CSPO - Certified Scrum Product Owner® Certification Certified Scrum Product Owner®(CSPO) Product Assumption Validation 1 — Questions and Answers
Question 1: 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?
- Add the premium analytics dashboard to the product roadmap and present it at the next Sprint Review
- Create a landing page describing the feature and measure how many users click 'Buy Now' before the feature exists (Correct answer)
- Ask the development team to estimate the cost of building the dashboard, then decide
- Survey existing users by email asking if they would pay more for analytics capabilities
Correct 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.
Question 2: Which statement BEST describes the difference between a validated assumption and a validated learning in product development?
- A validated assumption confirms a belief before building; a validated learning is insight gained after running an experiment (Correct answer)
- A validated assumption is documented in the product backlog; a validated learning is recorded in the Definition of Done
- A validated assumption requires stakeholder sign-off; a validated learning only requires the Product Owner's approval
- There is no meaningful difference — both terms refer to the same activity in Scrum
Correct 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.
Question 3: 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?
- Defer validating it until the team has more data from actual usage
- Validate it immediately, as high uncertainty combined with high impact makes it the riskiest assumption (Correct answer)
- Document it as an accepted risk and proceed with the Sprint
- Assign validation to a stakeholder outside the Scrum Team to avoid bias
Correct 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.
Question 4: 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?
- Declare the assumption validated because any improvement confirms the hypothesis
- Accept that the assumption was wrong and revert to the original onboarding flow permanently
- Treat the result as a falsified hypothesis, document the learning, and explore alternative explanations for drop-off (Correct answer)
- Extend the experiment for three more Sprints until the result becomes statistically significant
Correct 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.
Question 5: During backlog refinement, a stakeholder insists that 'everyone knows' users want dark mode, so no validation is needed. How should the Product Owner respond?
- Accept the stakeholder's claim since domain expertise counts as validation
- Agree to add dark mode to the next Sprint because stakeholder satisfaction is a key Scrum value
- 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 (Correct answer)
- Escalate the disagreement to the Scrum Master to resolve in the next retrospective
Correct 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.
Question 6: 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?
- Number of push notifications sent per day
- Seven-day retention rate of users who opted into notifications versus those who did not (Correct answer)
- Total app downloads in the week after notifications are enabled
- Number of support tickets mentioning push notifications
Correct 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.
CSPO - Certified Scrum Product Owner® Certification Certified Scrum Product Owner®(CSPO) Product Assumption Validation 1
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?