Domain 3 of 5

Goal Setting and Planning

The relationship between a product vision and a Product Goal, creating a Product Goal and a Sprint Goal, the components of a product plan or forecast, planning a release, and identifying small, valuable and usable increments.

4
Concepts
~20%
Of the exam
15
Practice questions
Concepts in this domain
01Product vision and what counts as a productA product is a vehicle to deliver value with a clear boundary, known stakeholders and well-defined users or customers.02The Product GoalThe single objective the Scrum Team plans against, and why a team holding three goals is holding none.03The Sprint GoalThe single objective for one Sprint, the Sprint Backlog's commitment, and the only thing in a Sprint the Developers actually promise.04Forecasting and release planningScrum prescribes no forecasting technique. What it defines is that the Sprint Goal is the commitment, and that projections come from observation.
Try a question from this domain

A CSPO course asks you to explain the relationship between a product vision and a Product Goal. Which explanation is correct?

  • AThey are two names for the same statement, one used internally and one externally.
  • BThe Product Goal is set first and the vision is derived from it once several goals have been achieved.
  • CThe vision is a Scrum artifact and the Product Goal is a stakeholder document.
  • DVision describes the long term future state of the product. The Product Goal is the single objective the Scrum Team is currently working toward on the way there, and it lives in the Product Backlog as its commitment.
15 questions on this domain.

One per page, with a worked explanation.

Start the set

Not affiliated with or endorsed by Scrum Alliance.