CSPO - Certified Scrum Product Owner® Certification Certified Scrum Product Owner®(CSPO) Product Vision and Strategy 1 — Questions and Answers
Question 1: How far into the future should a compelling product vision typically look?
- 3–6 months, aligned with the sprint cadence
- 1–2 years, matching the annual budget cycle
- 3–5 years or more, providing long-term directional clarity (Correct answer)
- Exactly 12 months, so it can be reviewed each fiscal year
Correct answer: 3–5 years or more, providing long-term directional clarity
A product vision is meant to inspire and guide long-term direction, typically spanning 3–5 years or more. Short timeframes like sprint cycles or annual budgets describe tactics, not vision.
Question 2: A Product Owner is preparing to share the product vision with a newly formed Scrum Team. Which approach best ensures the team understands and is aligned with the vision?
- Send a written vision document and ask the team to review it independently
- Present the vision once at kickoff and refer the team to the product backlog for details
- Facilitate a collaborative session where the team explores the vision and connects it to their work (Correct answer)
- Delegate vision communication to the Scrum Master so the Product Owner can focus on the backlog
Correct answer: Facilitate a collaborative session where the team explores the vision and connects it to their work
Shared understanding comes from active exploration, not passive reading or one-way broadcasts. A facilitated session lets the team internalize the vision and connect it meaningfully to their daily work.
Question 3: Which artifact most directly bridges a long-term product vision and the near-term items in the Product Backlog?
- The Sprint Goal
- The Definition of Done
- The product roadmap (Correct answer)
- The release burndown chart
Correct answer: The product roadmap
A product roadmap translates the strategic vision into a sequence of goals and milestones over time, giving context for why backlog items are prioritized as they are.
Question 4: A Product Owner discovers that the market has shifted significantly and the current product vision no longer reflects customer needs. What is the most appropriate response?
- Continue executing the existing vision to avoid confusing stakeholders
- Pause all sprints until a new vision is fully approved by leadership
- Revisit and update the vision collaboratively with stakeholders, then realign the product strategy (Correct answer)
- Delegate the vision update to the development team so the Product Owner can manage the backlog
Correct answer: Revisit and update the vision collaboratively with stakeholders, then realign the product strategy
Scrum embraces change. When market signals invalidate the vision, the Product Owner's responsibility is to update it through collaboration with stakeholders and then realign strategy and backlog accordingly.
Question 5: What is the relationship between a product goal (as described in the Scrum Guide) and the product vision?
- The product goal replaces the product vision once development begins
- The product vision and product goal are interchangeable terms for the same concept
- The product goal represents a concrete, near-term commitment that advances the product toward the broader vision (Correct answer)
- The product goal is set by the Scrum Master and is independent of the product vision
Correct answer: The product goal represents a concrete, near-term commitment that advances the product toward the broader vision
According to the Scrum Guide, the product goal is a near-term objective for the Scrum Team that sits on the path toward the longer-term product vision. Multiple product goals may be pursued in sequence to realize the vision.
Question 6: When crafting a product vision statement, which quality is most important for inspiring and guiding a Scrum Team?
- Technical precision about the implementation architecture
- Measurable KPIs and acceptance criteria
- A clear, customer-centric description of the desired future state (Correct answer)
- Detailed feature specifications for the first three releases
Correct answer: A clear, customer-centric description of the desired future state
A product vision should describe the future state from the customer's perspective in a way that is inspiring and direction-setting. Technical specs and KPIs belong in the strategy or backlog, not the vision itself.
CSPO - Certified Scrum Product Owner® Certification Certified Scrum Product Owner®(CSPO) Product Vision and Strategy 1
How far into the future should a compelling product vision typically look?