Scrum Artifacts and Commitments Flashcards
7 cards from real Professional Scrum Master practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Scrum Artifacts and Commitments flashcards as text
What is the PRIMARY purpose of the Product Goal in Scrum?
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.
A stakeholder asks why some Sprint Backlog items lack detailed descriptions early in the Sprint. What is the correct explanation?
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.
Which of the following is the commitment associated with the Increment?
Answer: Definition of Done
The Definition of Done is the commitment for the Increment, providing transparency about what quality standards must be met.
Can the Sprint Goal be changed once the Sprint has started?
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.
A team's Definition of Done only includes 'code written.' A Scrum Master identifies this as a problem. Why?
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.
Which artifact gives Developers a coherent target for each Sprint?
Answer: Sprint Goal
The Sprint Goal provides a coherent target for the Sprint, giving Developers flexibility in how they achieve it while maintaining focus.
A Product Owner frequently reorders the Product Backlog without explanation. What transparency issue does this create?
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.