SCRUM Definition of Done 1 — Questions and Answers
Question 1: What is the primary purpose of the Definition of Done in Scrum?
- To define the Sprint Goal for the team
- To create a shared understanding of what it means for work to be complete (Correct answer)
- To list all tasks remaining in the Sprint Backlog
- To document the team's historical velocity
Correct answer: To create a shared understanding of what it means for work to be complete
The Definition of Done creates a shared understanding of the quality standard required for a Product Backlog item to be considered complete by everyone on the Scrum Team.
Question 2: Who is responsible for creating the Definition of Done in Scrum?
- The Scrum Master alone
- The Product Owner alone
- The Scrum Team collectively, unless the organization already has one (Correct answer)
- External stakeholders and sponsors
Correct answer: The Scrum Team collectively, unless the organization already has one
The Scrum Team creates the Definition of Done; if the organization already has one, the team must at minimum comply with it and may add stricter criteria.
Question 3: What happens if a Product Backlog item does not meet the Definition of Done at the end of a Sprint?
- It is released with a known-issues note
- It is returned to the Product Backlog for future consideration (Correct answer)
- The Sprint is extended until it is complete
- The Scrum Master marks it done provisionally
Correct answer: It is returned to the Product Backlog for future consideration
Items that do not meet the Definition of Done cannot be released or presented at the Sprint Review and must be returned to the Product Backlog.
Question 4: The Definition of Done is described in the Scrum Guide as a formal description of:
- The Sprint Goal and success criteria
- The state of the Increment when it meets the quality measures required for the product (Correct answer)
- The team's working agreements and norms
- The release schedule for each increment
Correct answer: The state of the Increment when it meets the quality measures required for the product
The Scrum Guide defines the Definition of Done as a formal description of the state of the Increment when it meets the quality measures required for the product.
Question 5: If an organization already has a Definition of Done, what must a Scrum Team do with it?
- Ignore it and create their own from scratch
- Use it as a minimum standard and may add stricter criteria (Correct answer)
- Replace it entirely with a custom team version
- Get Product Owner approval before any deviation
Correct answer: Use it as a minimum standard and may add stricter criteria
Scrum Teams must comply with the organizational Definition of Done as a minimum and may extend it with additional, more rigorous criteria specific to their work.
Question 6: How does the Definition of Done contribute to transparency in Scrum?
- It makes the Sprint Backlog visible to all stakeholders in real time
- It ensures everyone has the same understanding of when work is truly complete (Correct answer)
- It publishes team velocity data on a public dashboard
- It reports the number of items completed during each Sprint
Correct answer: It ensures everyone has the same understanding of when work is truly complete
A shared Definition of Done creates transparency by ensuring all Scrum Team members and stakeholders share the same understanding of what 'complete' means.
Question 7: What is referred to as 'undone' work in the context of Scrum?
- Work that has been formally removed from the Sprint Backlog
- Work that is complete but not yet deployed to production
- Work that does not meet the Definition of Done by end of Sprint (Correct answer)
- Work that is assigned to the following Sprint by the Product Owner
Correct answer: Work that does not meet the Definition of Done by end of Sprint
'Undone' work refers to work that was started during a Sprint but did not meet the Definition of Done criteria by the Sprint's end.
SCRUM Definition of Done 1
What is the primary purpose of the Definition of Done in Scrum?