Definition of Done

5 minutes 5 Questions

When a Product Backlog item or an Increment is described as 'Done', everyone must understand what 'Done' means. Although the Scrum Guide doesn't prescribe a single universal definition of Done, the understanding of what Done means should be consistent across the Scrum Team. Every Increment must meet the team's current definition of 'Done'. This ensures that the quality of work is high. Any one Product Backlog item can be 'Done' only when it fits into the Increment, thus the definition of 'Done' becomes part of the convention of the Scrum Team.

Guide to Understanding and Answering Questions on 'Definition of Done' in PSM I Exam

The 'Definition of Done' is a key artifact in Scrum. It refers to the shared understanding within the Scrum Team about what it takes for a Product Backlog Item (PBI) or an Increment to be considered complete.

Importance: A clear Definition of Done helps in keeping the team on the same page, ensuring quality, and reducing rework. It promotes transparency and ensures that no task is marked as done without meeting the necessary standards.

How it works: The Definition of Done can vary depending on the team and the project. However, it should be mutually agreed by all team members, be visible and clear to everyone, and be reviewed and adapted regularly.

In an exam, you may come across questions testing your understanding of the Definition of Done.

Exam Tips: Here are some tips to help you answer questions on this topic:
- Remember, the Definition of Done is NOT the same as acceptance criteria.
- The Definition of Done applies to all items in the product backlog, not just a select few.
- In Scrum, Definition of Done is agreed upon by ALL team members, it’s not dictated by one person.
- Understand that the Definition of Done should be revisited and adapted as the team learns and improves.
Test mode:
Start practice test

PSM I - Definition of Done Example Questions

Test your knowledge of Definition of Done

Question 1

You have joined a new Agile team as a Scrum Master, and during the Sprint Review, you noticed the 'Definition of Done' is not being followed consistently. What is the best approach to handle this situation?

Correct Answer: Discuss the issue in the retrospective and work with the team to establish consistency

The correct approach is to address the issue during the retrospective and collaborate with the team to reinforce the importance of the 'Definition of Done' and establish consistency going forward.

Question 2

A team member constantly misunderstands the 'Definition of Done', resulting in unfinished tasks at the end of Sprints. How should this situation be approached?

Correct Answer: Address the issue during the next retrospective, clarifying any misunderstandings and offering assistance where necessary

In Scrum, issues such as misunderstandings of the 'Definition of Done' should be addressed collaboratively, with an emphasis on team discussion and improvement. The retrospective provides an ideal time for such discussions, focusing on process improvement and clarification of any misunderstandings without singling out individuals or implying blame. The wrong options, while related to team development and improvement, either shift responsibility away from collaborative problem solving, potentially isolate the team member, or imply punitive measures, all of which are contrary to the principles of Scrum.

Question 3

A Scrum team realizes mid-Sprint that an important aspect was overlooked in the 'Definition of Done', leading to a lower quality product. What should be the next step?

Correct Answer: Revise the 'Definition of Done' to include the overlooked aspect and address the impact on the current Sprint as a collaborative team effort.

When a Scrum team identifies an oversight in the 'Definition of Done' that affects product quality, the appropriate action is to collaboratively revise the 'Definition of Done' to incorporate the missing aspect and assess how it impacts the current Sprint. This ensures product quality is not compromised and that all stakeholders maintain a common understanding of what 'Done' means. Choosing to ignore the oversight, addressing it without team input, or taking actions that do not directly ameliorate the immediate issue in a collaborative manner do not align with Scrum principles of transparency, inspection, and adaptation.

More Definition of Done questions
18 questions (total)
Start 18 question test

Other Scrum Artifacts concepts

Product BacklogProduct GoalProduct OwnerScrum BoardSprint BacklogSprint BurndownSprint GoalSprint RetrospectiveSprint Review
All Scrum Artifacts questions · PSM I practice test