In scrum, the Development Team defines done. However, the Scrum Master and Product Owner should also contribute to creating the team’s definition of done.
In addition, before a scrum team finalize its definition of done, they may want to consider input from testers.
Creating a definition of done in scrum is not a single individual responsibility. It must be created through a collaborative effort and consensus among the scrum team.
This collaborative approach ensures that everyone involved understands and agrees on what it means for work to be considered complete.
Let’s take a look at other things you need to know about the definition of done in scrum.
What is the definition of done in scrum?
The definition of done (DoD) in scrum is a clear and concise list of criteria a product increment must meet before the team considers it complete.
It ensures all work is fully finished and ready for delivery, minimizing the risk of releasing incomplete features.
The DoD includes all necessary steps such as coding, code review, testing, documentation, and other activities required to achieve a potentially shippable product increment.
Generally, you can say DoD acts as a quality gate, ensuring that increments meet a consistent standard.
Is the definition of done necessary?
Yes, the definition of done is crucial in scrum. It provides a shared understanding of what it means to finish work, aligning the team’s expectations and reducing ambiguities.
Without a clear DoD, different team members might have varying interpretations of completeness. This will lead to inconsistencies and potential rework.
The fact is that a well-defined DoD contributes to the overall success of your scrum team. It helps maintain quality, ensures transparency, and fosters accountability within the team.
When is the definition of done created in scrum?
The definition of done is typically created at the beginning of a project, during the initial sprint planning sessions.
It is a collaborative effort, involving the entire Scrum Team to ensure that everyone’s perspectives are considered.
DoD is not a create-and-forget document. It should evolve, adapting to new insights and changes in project requirements.
The team must review regularly and refine as needed during sprint retrospectives to ensure it remains relevant and effective.
Who is responsible for work done in scrum?
Only the Development Team is responsible for delivering work that meets the definition of done. They ensure that each increment meets all the criteria outlined in the DoD.
However, the entire scrum team, including the Product Owner and Scrum Master, has a role in defining, understanding, and maintaining the DoD.
The Product Owner ensures that the definition of done aligns with the product goals and customer requirements.
The Scrum Master, on the other hand, facilitates the process and helps the team adhere to it. Therefore, it’s a continuous collaborative effort.
Who checks the definition of done?
In scrum, the Development Team defines done and is also responsible for checking the definition of done during each sprint. This practice ensures that all completed work meets the agreed-upon criteria.
In addition, the Product Owner also reviews the work to confirm that it fulfils the acceptance criteria and aligns with the overall product vision.
Regular inspections ensure that the quality standards are consistently met and maintained.
Definition of done vs acceptance criteria
The definition of done and acceptance criteria serve different purposes in scrum. The DoD is a general checklist that applies to all product increments, ensuring they are complete and shippable.
Acceptance Criteria (AC), on the other hand, are specific to individual user stories or tasks. The AC details the conditions those items must meet to be accepted by the Product Owner.
So, while acceptance criteria focus on specific functionality, the DoD encompasses broader aspects of quality and completeness.
Definition of done checklist example
While the developers are the one who defines done, it’s important to take inputs from other members of the scrum team. As a result, the DoD checklist should include non-technical items.
From my experience as a Scrum Master, below are some of the items that should be on a scrum team’s definition of done.
- Acceptance criteria met
- Code reviewed
- All tests passed
- Correct UI components used
- Successful deployment in all environments
- QA completed and issues resolved
- Documentation completed
- Tested and signed off by the Product Owner
Some of the items above have more parts than others. For example, testing includes penetration tests, performance tests, unit tests, tests on browsers and devices, etc.
Regardless of how comprehensive the definition of done is, it must ensure nothing less than a high-quality product is delivered.
This is the purpose of DoD, and the scrum team must tailor it to ensure their product meets every required and necessary standard.
Why do we need the definition of done?
For every scrum team, the definition of done is essential for ensuring high-quality, consistent deliverables in scrum.
It reduces misunderstandings about what “done” means, aligns the team’s efforts, and ensures that all work meets a minimum quality standard.
A clear DoD helps scrum teams prevent incomplete or subpar increments from being released. Unless an increment meets the DoD, it shouldn’t be released.
As a result, the team protects the product’s integrity and enhances customer satisfaction. This also promotes a culture of accountability and continuous improvement within the team.
The definition of done serves which three purposes?
The definition of done serves three primary purposes:
- Ensuring quality
- Providing clarity
- Facilitating alignment
Firstly, DoD ensures that all increments meet a consistent quality standard. Secondly, it provides clarity by defining what “done” means, reducing ambiguity.
Lastly, it facilitates alignment among team members and stakeholders, ensuring everyone has a shared understanding of what constitutes a complete product increment.
Conclusion: Is the definition of done worth It?
Absolutely, the definition of done is worth it in Scrum. It is a foundational element that supports the delivery of high-quality, reliable products.
Providing a clear, shared understanding of completeness, enhances team collaboration, ensures consistency, and maintains the integrity of the product.
Therefore, if you’re passionate about consistently delivering high-quality products, a detailed definition of done is a must for your scrum team.
While the Development Team defines done, it must be a collaborative effort including the Product Owner, Scrum Master, and inputs from testers and even designers if necessary.
Furthermore, the team should review their definition of done to keep it relevant, effective, and aligned with the product’s vision.
Here’s a post on all you need to know about daily scrum.
I hope you found this post helpful.
