Organization DoD

is aDefintion of Done, Organization Artefact
definesProduct Development Process of Organization
constraintsPortfolio Backlog Item
is created byOrganization Scrum Master
is adapted inOrganization Retrospective

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 portfolio-level DoD for the entire Organization.

Everyone needs to have a common understanding of when work is done to ensure transparency.

The Organizational DoD is the quality promise of the Organization

The DoD also leads the Cluster System Engineer Group (CSEG) when deciding how many Portfolio Backlog entries it can pull into the Cycle Backlog during Portfolio Planning. 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. Organizations deliver an increment of results, knowledge and / or system functionality in each cycle. This increment is fully usable, so the Portfolio Owner can choose to release it at any time.

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. 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. If there are several Clusters working on the same system, all Clusters must 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. Mature Organizations are expected to expand their respective definition-of-done appropriately to ensure stricter criteria for higher quality.

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 product development process are also defined via the DoD.

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.



Further suitable links:

Events Roles Groups Artifacts
Portfolio Planning

Organisation Sync

Portfolio Refinement

Portfolio Review

Organisation Retrospective

Portfolio Owner

Portfolio Architect

Organisation Scrum Master

Cluster Product Owner Group

Cluster System Engineer Group

Cluster Scrum Master Group

Organisation Management Circle

Team DoD


Cluster DoD


Portfolio Backlog

Systems & Applications

System Platforms & Variants

Organisation Improvement Backlog