{"id":665,"date":"2019-08-21T22:41:00","date_gmt":"2019-08-21T20:41:00","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=665"},"modified":"2026-03-19T12:30:04","modified_gmt":"2026-03-19T11:30:04","slug":"dod","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/dod\/","title":{"rendered":"Team DoD (Definition of Done)"},"content":{"rendered":"

The <\/span><\/span>Team<\/span><\/span><\/a> , the <\/span><\/span>Team Product Owner<\/span><\/span><\/a> and the <\/span><\/span>Stakeholders<\/span><\/span><\/a> must agree on what it means when a backlog entry or a result is referred to as “done”. <\/span>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. <\/span>This is realized through the definition-of-done of the respective <\/span><\/span>Team<\/span><\/span><\/a> , <\/span><\/span>Cluster<\/span><\/span><\/a> or <\/span><\/span>Organization<\/span><\/span><\/a> .<\/span><\/span><\/p>\n

The DoD is the team’s promise of quality<\/span><\/span><\/h2>\n

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<\/a>. <\/span>The purpose of each Iteration<\/a> is to provide inspectable results, <\/span><\/span>Usable Knowledge,<\/span><\/span><\/a> or <\/span><\/span>potentially deliverable Features<\/span><\/span><\/a> within a <\/span><\/span>System Increment<\/span><\/span><\/a> that correspond to the current Definition-of-done. <\/span>Working Teams deliver an increment of results, knowledge and \/ or <\/span><\/span>system functionality<\/span><\/span><\/a> in each Iteration <\/span>. <\/span>This increment is fully verfied and usable, so the Team Product Owner can choose to release it at any time.<\/span><\/span><\/p>\n

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 <\/span><\/span>Cluster DoD<\/span><\/span><\/a> as a minimal goal. <\/span>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. <\/span>If there are several teams working on the same system, all teams have to create a definition of done together. <\/span>Each System Increment is additive to all previous increments and has been thoroughly tested to ensure that all increments work together. <\/span>More mature Teams are expected to adjust their respective Definition-of-done appropriately to ensure stricter criteria for higher quality. <\/span>New entries in the Definition-of-done can result in work to be done being uncovered in earlier “done” system increments.\u00a0<\/span><\/span><\/p>\n

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<\/a> to be created for the product development process are also defined via the DoD.<\/span><\/span><\/p>\n

The DoD therefore is the essence of the process descriptions and “standard operation procedures” of a classic organization, but in a strongly condensed form.<\/span><\/p>\n

.<\/span><\/span><\/span><\/p>\n

\n

Further suitable links:<\/p>\n\n\n\n\n
Events<\/td>\nRoles<\/td>\nGroups<\/td>\nArtifacts<\/td>\n<\/tr>\n
Team Planning<\/a><\/p>\n

Team Sync<\/a><\/p>\n

Team Backlog Refinement<\/a><\/p>\n

Team Review<\/a><\/p>\n

Team Retrospective<\/a><\/td>\n

Team Product Owner<\/a><\/p>\n

Team System Engineer<\/a><\/p>\n

Team Scrum Master<\/a><\/td>\n

Working Team<\/a><\/p>\n

Community of Practice<\/a><\/td>\n

Team Backlog<\/a><\/p>\n

Inspectable Results<\/a><\/p>\n

Team Improvement Backlog<\/a><\/p>\n

.<\/span><\/p>\n

Cluster DoD<\/a><\/p>\n

.<\/span><\/p>\n

Organisation DoD<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"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…","protected":false},"author":3,"featured_media":1429,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4,21],"tags":[358,369,431],"translation":{"provider":"WPGlobus","version":"2.10.10","language":"en","enabled_languages":["de","en"],"languages":{"de":{"title":true,"content":true,"excerpt":false},"en":{"title":true,"content":true,"excerpt":false}}},"_links":{"self":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/665"}],"collection":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=665"}],"version-history":[{"count":24,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/665\/revisions"}],"predecessor-version":[{"id":5280,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/665\/revisions\/5280"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/1429"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=665"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=665"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=665"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}