CSPO Product Assumption Validation 4 â Questions and Answers
Question 1: A startup PO has limited budget and needs to validate whether their target segment will use a new expense tracking feature. The FASTEST low-cost experiment is:
- Build the full feature in one sprint and measure usage
- Create a fake door test: add the feature button to the UI and measure click-through before building it (Correct answer)
- Commission a market research firm to survey 1,000 users
- Ask the sales team to pitch the feature in demos and count positive reactions
Correct answer: Create a fake door test: add the feature button to the UI and measure click-through before building it
A fake door (or 404) test measures genuine interest by tracking clicks on a feature that doesn't yet exist, at near-zero development cost.
Question 2: Which statement BEST reflects the Scrum framework's stance on assumption validation?
- Scrum has no explicit process for assumption validation; it is an agile anti-pattern
- Scrum's inspect-and-adapt cycles and Sprint Reviews provide natural checkpoints for validating product assumptions (Correct answer)
- Assumptions should only be validated during the initial product discovery phase, not during active sprints
- The Scrum Master is responsible for identifying and validating all product assumptions
Correct answer: Scrum's inspect-and-adapt cycles and Sprint Reviews provide natural checkpoints for validating product assumptions
Scrum's empirical pillars â transparency, inspection, and adaptation â inherently support ongoing assumption validation through short feedback loops.
Question 3: A PO assumes that reducing checkout steps from 5 to 3 will increase conversion. After shipping the change, conversion drops. What is the MOST likely explanation?
- The development team made coding errors
- An underlying assumption (e.g., that removed steps caused friction rather than building trust) was incorrect (Correct answer)
- The experiment was not run long enough
- The PO should have consulted the Scrum Master before making this change
Correct answer: An underlying assumption (e.g., that removed steps caused friction rather than building trust) was incorrect
Unexpected results often reveal that a hidden assumption about user psychology or behavior was incorrect, requiring further investigation.
Question 4: What does 'desirability testing' specifically validate in the context of product assumption validation?
- Whether the technical architecture can support the feature at scale
- Whether users actually want the product or feature and perceive it as valuable (Correct answer)
- Whether the business model generates sufficient margin
- Whether the development team can build the feature within constraints
Correct answer: Whether users actually want the product or feature and perceive it as valuable
Desirability testing focuses on the user dimension â confirming that real users want the solution and find it valuable enough to adopt.
Question 5: A PO is conducting assumption validation experiments during a sprint. How should this work appear in the Sprint Backlog?
- It should not appear â experiments are not sprint work
- As explicit Sprint Backlog items with a clear hypothesis, test method, and success criteria (Correct answer)
- Only as a note in the Sprint Goal
- Bundled into the definition of done for related user stories
Correct answer: As explicit Sprint Backlog items with a clear hypothesis, test method, and success criteria
Making experiments explicit Sprint Backlog items with defined success criteria keeps validation work transparent and actionable for the whole team.
Question 6: When a PO presents assumption validation results at a Sprint Review, what is the stakeholders' PRIMARY role?
- To formally approve or reject the validated learning
- To provide additional context, surface related assumptions, and help interpret the evidence (Correct answer)
- To assign new assumptions for the next sprint
- To evaluate whether the experiment was designed correctly
Correct answer: To provide additional context, surface related assumptions, and help interpret the evidence
Stakeholders bring domain knowledge and business context that enriches interpretation of validation results and helps surface further unknowns.
Question 7: A PO documents the following: 'We believe [users] will [perform this action] because [reason]. We will know this is true when [measurable outcome].' This is an example of:
- A Definition of Done criterion
- A hypothesis statement format for structured assumption validation (Correct answer)
- A user story acceptance criterion
- A Sprint Goal template
Correct answer: A hypothesis statement format for structured assumption validation
This structured hypothesis format ensures assumption validation experiments are specific, testable, and tied to measurable outcomes.
CSPO Product Assumption Validation 4
A startup PO has limited budget and needs to validate whether their target segment will use a new expense tracking feature.
The FASTEST low-cost experiment is: