{"id":1178,"date":"2019-10-10T21:39:46","date_gmt":"2019-10-10T19:39:46","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=1178"},"modified":"2026-03-19T12:30:55","modified_gmt":"2026-03-19T11:30:55","slug":"portfoliodod","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/portfoliodod\/","title":{"rendered":"Organization DoD"},"content":{"rendered":"

The <\/span><\/span>teams of<\/span><\/span><\/a> all <\/span><\/span>Clusters in<\/span><\/span><\/a> the <\/span><\/span>organization<\/span><\/span><\/a> , the <\/span><\/span>Cluster System Engineer Group<\/span><\/span><\/a> , the <\/span><\/span>Cluster Product Owner Group<\/span><\/span><\/a> and the <\/span><\/span>stakeholders<\/span><\/span><\/a> must understand what it means when a <\/span><\/span>backlog entry<\/span><\/span><\/a> or a result is referred to as “done”. <\/span>Although the <\/span><\/span>Cluster DoDs<\/span><\/span><\/a> can <\/span>differ<\/span><\/a> significantly from Cluster to cluster, there is only one portfolio-level DoD for the entire Organization.<\/span><\/span><\/p>\n

Everyone needs to have a common understanding of when work is done to ensure transparency.<\/span><\/span><\/p>\n

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

The DoD also leads the <\/span><\/span>Cluster System Engineer Group (CSEG)<\/span><\/span><\/a> when deciding how many Portfolio Backlog entries it can pull into the Cycle Backlog during Portfolio Planning. <\/span>The purpose of each Portfolio Cycle is to deliver potentially deliverable functionality within application versions and system increments that correspond to the current definition of done. <\/span>Organizations deliver an increment of results, knowledge and \/ or system functionality in each cycle. <\/span>This increment is fully verified and usable, so the Portfolio Owner 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 product 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>Mature Organizations are expected to expand their respective definition-of-done appropriately to ensure stricter criteria for higher quality.<\/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 product development process are also defined via the DoD.<\/span><\/span><\/p>\n

The definition of done therefore corresponds in its essence, 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

 <\/p>\n

\n

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

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

Portfolio Refinement<\/a><\/p>\n

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

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

Portfolio Owner<\/a><\/p>\n

Portfolio Architect<\/a><\/p>\n

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

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

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

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

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

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

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

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

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

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

Systems & Applications<\/a><\/p>\n

System Platforms & Variants<\/a><\/p>\n

Organisation Improvement Backlog<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"The teams of all Clusters in the organization , the Cluster System Engineer Group , the Cluster Product Owner Group and the stakeholders must understand what it means when a backlog entry or a result is referred to as “done”. Although the Cluster DoDs can differ significantly from Cluster to cluster, there is only one…","protected":false},"author":3,"featured_media":1429,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4,23],"tags":[50,369,279],"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\/1178"}],"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=1178"}],"version-history":[{"count":28,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1178\/revisions"}],"predecessor-version":[{"id":5281,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1178\/revisions\/5281"}],"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=1178"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=1178"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=1178"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}