If you ask the members of a scrum team what they expect to see when a requirement is done, you get as many answers as there are team members. To avoid confusion and ensure quality, teams must reach consensus and define exactly what “done” means for every requirement.
The definition of done is unique to each team and product—there’s no universal standard. But without it, estimation and quality suffer.
Before starting a product development effort, scrum teams define what it means for a requirement to be developed and tested to a releasable state with a definition of done. Until you have a consensus on this definition, estimations will be based on varying assumptions.
For each requirement within a sprint, you complete the following types of development work:
- Requirement elaboration
- Design
- Development
- Comprehensive testing
- Integration
- Documentation
- Approval
What are the risks if team members have different ideas of what “done” means?
This definition of done needs to be specific, refined, and focused on what it means to do these things to completion to achieve the level of quality you’re striving for in your product. Consider the outcomes you’re striving to accomplish.
Effective definitions of done encompass these four factors:
- Developed: The product has been fully developed by the team.
- Tested: The team fully tested the product to ensure it functions properly.
- Integrated: The product has been fully integrated within the product as a whole and any related products.
- Documented: The developers create whatever documentation is needed. Just remember that the goal is “barely sufficient.”
A shared agreement within the scrum team on what it means for a requirement to be completed and ready for release.
When you’ve come up with your definition of done, write it out on a white poster board and tape it to the wall or make it your virtual background, and radiate it for the entire product team to see. You’ll always have it right in front of the developers and product owner. We call it in-your-face documentation. No cover sheet, no table of contents — simply the lowest-fidelity way that communicates and makes the information the most visible.
How could you display your team’s definition of “done” so everyone sees it daily?
In your definition of done, in addition to the development, consider the depth of testing and documentation you might need. You might consider the following types of testing:
- Component
- Functional
- Integration
- Security
- Regression
- User acceptance
The process of making a set of marketable features available outside the scrum team—either to users, stakeholders, or the wider market.
Also, consider the documentation you need:
- Technical
- User
- Maintenance
Want to go deeper? The science behind team alignment on “done”
Research in agile teams shows that clear, visible standards like the definition of done improve estimation accuracy and reduce defects. When teams regularly review and update their definition together, it fosters ownership and reduces confusion.
- Scrum teams must agree on a definition of done before estimating or starting work.
- The definition should cover development, testing, integration, and documentation.
Each point may differ between the sprint and release levels, though we prefer the sprint-level definition of done to include everything necessary to release. You also may have organizationally specific items that you want to include. It’s your choice. The point is to have a clear definition of done that’s defined by the scrum team.
The definition of “done” is just a checklist that can be copied from project to project.
Each team must thoughtfully craft its own definition of “done” to match its goals, products, and context.
In a fintech startup, the scrum team’s definition of done included passing a security audit, user documentation, and integration with internal APIs—ensuring quality and regulatory compliance at every sprint.
A release occurs when a set of marketable features is released outside the scrum team. This could happen several times during a sprint, at the end of each sprint, or after a series of sprints. These requirements may be released into the market and to the users, or they may go to internal or external stakeholders for real-world use and feedback.
Practitioners recommend revisiting and refining the definition of done at regular intervals, especially after releases or major changes.
A regular sprint entails completing the development, testing, documentation, and approving items in the sprint backlog. However, before doing a product release, other activities may be needed that the developers wouldn’t have access to in a regular sprint. Therefore, sometimes scrum teams have a release sprint just before the release itself to allow these additional steps to be addressed. The key is the requirements must work and be demonstrable at the end of every sprint. You can inspect and tune for scale in the release sprint, but the requirements must work every sprint.
What kinds of testing or documentation might be unique to your team’s “done” criteria?
What are the four factors in an effective definition of “done”?
Tap to revealDeveloped, Tested, Integrated, Documented.
Why is a consensus on the definition of “done” important?
Tap to revealIt ensures accurate estimation and prevents misunderstandings, leading to higher product quality.
What is the goal for documentation in the definition of “done”?
Tap to revealThe goal is “barely sufficient” documentation—enough to meet needs, but no excess.
Work with your team or solo to create a visible, actionable definition of “done” for your current project.
- List the steps your team completes before considering a requirement finished.
- Write these steps as a clear, visible definition—use a poster board or digital board.
- Share it with your team and revise it together for clarity and completeness.
What challenges might arise when creating a definition of “done” for your team, and how would you address them?
Reflect on a time when your team lacked a clear definition of “done.” What consequences did this have, and what would you change if you could rewrite that experience?
A clear, visible definition of done is essential for scrum teams to achieve quality, alignment, and accurate estimation.
The definition of done should be regularly reviewed and refined to match the evolving needs and standards of the team and product.
This definition of done needs to be specific, refined, and focused on what it means to do these things to completion to achieve the level of quality you’re striving for in your product.
Which factor is NOT one of the four core elements in an effective definition of “done”?
How confident are you that you can list and explain the four factors in a definition of “done”?
The Shift
- A shared and visible definition of done aligns scrum teams and boosts product quality.
- Effective definitions cover development, testing, integration, and documentation—tailored for each team.
- Regularly revisiting and refining your definition keeps it relevant and actionable.