{"id":1076,"date":"2019-10-05T20:00:55","date_gmt":"2019-10-05T18:00:55","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=1076"},"modified":"2026-03-19T12:29:19","modified_gmt":"2026-03-19T11:29:19","slug":"clusterdod","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/clusterdod\/","title":{"rendered":"Cluster DoD"},"content":{"rendered":"

The Teams<\/a> of the <\/span><\/span>Cluster<\/span><\/span><\/a> , the <\/span><\/span>Team System Engineer Group<\/span><\/span><\/a> , the <\/span><\/span>Team Product Owner Group<\/span><\/span><\/a> and the <\/span><\/span>Stakeholders<\/span><\/span><\/a> must agree on what it means when a Backlog Item or a result is marked as “done”. <\/span>Although this can vary significantly from Cluster to cluster, everyone must have a common understanding of when work is done to ensure transparency. <\/span>This is done through the <\/span><\/span>Definition-of-done<\/span><\/span><\/strong> of<\/span><\/span> the respective Cluster.<\/span><\/span><\/p>\n

The Cluster DoD is the quality promise of the Cluster<\/span><\/span><\/h2>\n

The DoD also guides the Team System Engineer Group<\/a> in deciding how many Cluster Backlog Items it can pull into the Cycle Backlog during Cluster Planning<\/a>. <\/span>The purpose of each Cycle<\/a> is to provide Inspectable Results, Usable Knowledge, or potentially deliverable functionality within a System Increment that correspond to the current Definition-of-done. <\/span>Clusters provide an increment of results, knowledge and \/ or system functionality in each Cycle. <\/span>This increment is fully verfied and usable so that the Cluster Product Owner<\/a> can choose to release it at any time.<\/span><\/span><\/p>\n

If the Definition-of-done for a product is part of an organization’s conventions, standards, or guidelines, all Clusters must follow them as a minimum goal. <\/span>If “Done” for a result is not part of the organization’s convention, the Cluster (ie the TSEG) must formulate a definition-of-done that is appropriate for the product. <\/span>If there are several Clusters working on the same system, all Clusters must 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 Clusters are expected to expand their respective definition-of-done appropriately to ensure stricter criteria for higher quality. <\/span>New entries in the definition-of-done can cause<\/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><\/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
Cluster Planning<\/a><\/p>\n

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

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

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

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

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

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

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

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

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

Team Scrum Master Group<\/a><\/p>\n

Cluster Management Circle<\/a><\/td>\n

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

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

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

Usable Knowledge<\/a> & System Increment<\/a><\/p>\n

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

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

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

 <\/p>\n","protected":false},"excerpt":{"rendered":"The Teams of the Cluster , the Team System Engineer Group , the Team Product Owner Group and the Stakeholders must agree on what it means when a Backlog Item or a result is marked as “done”. Although this can vary significantly from Cluster to cluster, everyone must have a common understanding of when work…","protected":false},"author":3,"featured_media":1429,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4,20,22],"tags":[369],"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\/1076"}],"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=1076"}],"version-history":[{"count":22,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1076\/revisions"}],"predecessor-version":[{"id":2300,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1076\/revisions\/2300"}],"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=1076"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=1076"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=1076"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}