Team DoD (Definition of Done)

is aDefintion of Done, Team Artefact
definesProduct Development Process of Team
constraintsTeam Backlog Item
is created byTeam Scrum Master
is adapted inTeam Retrospective

The Team , the Team Product Owner and the Stakeholders must agree on what it means when a backlog entry or a result is referred to as “done”. Although this can vary significantly from team to team, all Team Members must have a common understanding of when work is done to ensure transparency. This is realized through the definition-of-done of the respective Team , Cluster or Organization .

The DoD is the team’s promise of quality

The DoD also guides the Working Team in deciding how many Team Backlog Items it can pull into the Iteration Backlog during the Team Planning. The purpose of each Iteration is to provide inspectable results, Usable Knowledge, or potentially deliverable Features within a System Increment that correspond to the current Definition-of-done. Working Teams deliver an increment of results, knowledge and / or system functionality in each Iteration . This increment is fully usable, so the Team Product Owner can choose to release it at any time.

If the Definition-of-done for a Team is part of the conventions, standards, or guidelines of the Cluster or Organization, all Teams must use this Cluster DoD as a minimal goal. If “done” for a Team is not part of the convention of the Cluster or Organization, the Team must formulate a Definition-of-done that is appropriate for the Team results. If there are several teams working on the same system, all teams have to create a definition of done together. Each System Increment is additive to all previous increments and has been thoroughly tested to ensure that all increments work together. More mature Teams are expected to adjust their respective Definition-of-done appropriately to ensure stricter criteria for higher quality. New entries in the Definition-of-done can result in work to be done being uncovered in earlier “done” system increments. 

Every single result, product or system should have a Definition of done, which is the standard for any work performed on it. Often, the documents to be created for the product development process are also defined via the DoD.

The DoD therefore is the essence of the process descriptions and “standard operation procedures” of a classic organization, but in a strongly condensed form.


Further suitable links:

Events Roles Groups Artifacts
Team Planning

Team Sync

Team Backlog Refinement

Team Review

Team Retrospective

Team Product Owner

Team System Engineer

Team Scrum Master

Working Team

Community of Practice

Team Backlog

Inspectable Results

Team Improvement Backlog


Cluster DoD


Organisation DoD