Professional Scrum Master Scrum Artifacts and Commitments 2 — Questions and Answers
Question 1: A new team member asks where the Product Goal is documented. What is the correct answer?
- In the Sprint Backlog
- In the Product Backlog (Correct answer)
- In the team wiki
- In the Sprint Review notes
Correct answer: In the Product Backlog
The Product Goal is part of the Product Backlog — it is the long-term objective the Product Backlog describes how to achieve.
Question 2: The Scrum Team completes a Sprint but the Increment does not meet the Definition of Done. What happens to that work?
- It is released anyway with a disclaimer
- It is deleted from the Product Backlog
- It is not included in the Increment and returned to the Product Backlog (Correct answer)
- It is moved to the next Sprint as a priority item
Correct answer: It is not included in the Increment and returned to the Product Backlog
Work that does not meet the Definition of Done cannot be part of the Increment and must be returned to the Product Backlog for future consideration.
Question 3: Which statement BEST describes the relationship between the Sprint Goal and the Sprint Backlog?
- The Sprint Goal is a summary of every item in the Sprint Backlog
- The Sprint Backlog is the plan for achieving the Sprint Goal (Correct answer)
- The Sprint Goal replaces the Sprint Backlog once committed
- The Sprint Backlog and Sprint Goal are created in different events
Correct answer: The Sprint Backlog is the plan for achieving the Sprint Goal
The Sprint Backlog consists of the Sprint Goal, selected Product Backlog items, and the plan for delivering the Increment — so the backlog is the plan to achieve the goal.
Question 4: A Product Owner wants to remove the Definition of Done to ship faster. As Scrum Master, what do you do?
- Allow it since the Product Owner has final authority over releases
- Explain that the Definition of Done is mandatory and ensures transparency (Correct answer)
- Escalate to senior management
- Replace it with a shorter checklist instead
Correct answer: Explain that the Definition of Done is mandatory and ensures transparency
The Definition of Done is a formal commitment in Scrum that creates transparency and ensures the Increment is truly done — it cannot simply be removed.
Question 5: During Sprint Planning, the team cannot agree on a Sprint Goal. What should happen?
- Skip the Sprint Goal and start working on backlog items
- The Scrum Master assigns a Sprint Goal
- Continue the discussion until a meaningful Sprint Goal is agreed upon (Correct answer)
- Use last Sprint's goal as a default
Correct answer: Continue the discussion until a meaningful Sprint Goal is agreed upon
The Sprint Goal must be finalized during Sprint Planning — it is the commitment of the Sprint Backlog and cannot be skipped.
Question 6: What makes the Product Backlog an artifact that supports transparency?
- It is hidden from stakeholders to protect the team
- It is visible to all and represents the single source of work for the Scrum Team (Correct answer)
- It is updated only at Sprint Reviews
- It contains only completed features
Correct answer: It is visible to all and represents the single source of work for the Scrum Team
The Product Backlog is an emergent, ordered list visible to all stakeholders, making the upcoming work transparent to everyone.
Question 7: An organization has multiple Scrum Teams working on the same product. How many Definitions of Done should exist?
- One per Scrum Team
- One per Sprint
- One shared Definition of Done for all teams on the product (Correct answer)
- Each team decides independently with no coordination
Correct answer: One shared Definition of Done for all teams on the product
Multiple teams on the same product must share a single Definition of Done so their Increments can be combined into a coherent whole.
Professional Scrum Master Scrum Artifacts and Commitments 2
A new team member asks where the Product Goal is documented.
What is the correct answer?