Professional Scrum Master Scrum Artifacts and Commitments 3 — Questions and Answers
Question 1: What is the PRIMARY purpose of the Product Goal in Scrum?
- To define the team's velocity for the year
- To give the Scrum Team a long-term objective to plan toward (Correct answer)
- To list all features the product will ever have
- To set the budget for product development
Correct answer: To give the Scrum Team a long-term objective to plan toward
The Product Goal describes the future state of the product and serves as a long-term objective the Scrum Team plans and works toward.
Question 2: A stakeholder asks why some Sprint Backlog items lack detailed descriptions early in the Sprint. What is the correct explanation?
- The team is behind on documentation
- The Sprint Backlog is updated as more is learned — items are refined throughout the Sprint (Correct answer)
- Only Done items need descriptions
- Scrum forbids writing requirements
Correct answer: The Sprint Backlog is updated as more is learned — items are refined throughout the Sprint
The Sprint Backlog is updated throughout the Sprint as the Developers learn more — it is a living plan, not a frozen document.
Question 3: Which of the following is the commitment associated with the Increment?
- Product Goal
- Sprint Goal
- Definition of Done (Correct answer)
- Acceptance Criteria
Correct answer: Definition of Done
The Definition of Done is the commitment for the Increment, providing transparency about what quality standards must be met.
Question 4: Can the Sprint Goal be changed once the Sprint has started?
- Yes, the Product Owner can change it at any time
- Yes, but only with stakeholder approval
- No, the Sprint Goal is fixed for the duration of the Sprint (Correct answer)
- Yes, the Developers can update it daily
Correct answer: No, the Sprint Goal is fixed for the duration of the Sprint
The Sprint Goal is set during Sprint Planning and does not change — only in extreme circumstances would a Sprint be cancelled rather than the goal changed.
Question 5: A team's Definition of Done only includes 'code written.' A Scrum Master identifies this as a problem. Why?
- It creates too much work for the Developers
- It lacks quality criteria needed to produce a potentially releasable Increment (Correct answer)
- It should be created by the Product Owner, not the team
- Definitions of Done must have at least 10 items
Correct answer: It lacks quality criteria needed to produce a potentially releasable Increment
A Definition of Done with only 'code written' does not ensure the Increment is of releasable quality, undermining the transparency and value of the artifact.
Question 6: Which artifact gives Developers a coherent target for each Sprint?
- Product Goal
- Sprint Goal (Correct answer)
- Definition of Done
- Release Plan
Correct answer: Sprint Goal
The Sprint Goal provides a coherent target for the Sprint, giving Developers flexibility in how they achieve it while maintaining focus.
Question 7: A Product Owner frequently reorders the Product Backlog without explanation. What transparency issue does this create?
- Developers lose sprint velocity metrics
- Stakeholders and Developers cannot understand the rationale behind priorities (Correct answer)
- The Sprint Goal automatically changes
- The Definition of Done becomes invalid
Correct answer: Stakeholders and Developers cannot understand the rationale behind priorities
Unexplained reordering reduces transparency — stakeholders and Developers need to understand why items are prioritized to inspect and adapt effectively.
Professional Scrum Master Scrum Artifacts and Commitments 3
What is the PRIMARY purpose of the Product Goal in Scrum?