Artefacts

Cluster DoD

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…

Cluster Improvement Backlog

The Improvement Backlog describes the supply of improvements and is integrated into the work planning by the relevant group, self-organized. A rule that describes how much work the group spends on improvements (e.g. 10-20%) helps to keep the predictabilityof other Backlog Items high. The Improvement Backlog is the planning and structuring tool of the Scrum…

Cluster Mission

Content of a Mission The mission covers the areas of responsibility (the What) and the culture and standards of behavior (the How). The mission clarifies the following points: What is our self-image. What is the purpose of the team? How does the team position itself within the cluster and the organization? How do we want…

Definition of done (generic)

Everyone needs to have a common understanding of when work is done to ensure transparency. The Definition-of-Done is a promise of quality The DoD is derived from the idea of the Acceptance Criteria of Backlog Items. It describes which types of results must be present and which work must have been performed in order for…

Definition of Ready (DoR)

The definition-of-ready (DoR) is a list that defines which criteria certain artifacts must meet before defined actions start in the organizational unit (Team, Group, Cluster). It is an agreement to set clear quality criteria for artifacts. In the P4 framework, a team shouldn’t pull unestimated Backlog Items into an Iteration. DoRs exist at all levels…

Design Jounal

A design journal is usually created for each system/product/application. In the format of a logbook, it contains … all design changes that have been made. For each selected and implemented solution: The reasons that led to the change, and the solution options considered (with an analysis of the pros and cons). The contents of the…

The Mission for Teams, Cluster and the Organization

The mission covers the areas of responsibility (the What) and the culture and standards of behavior (the How). The mission clarifies the following points: What is our self-image. What is the purpose of the team? How does the team position itself within the cluster and the organization? How do we want to work together internally…

Documentation of Product and Process

“We favor working software over comprehensive documentation”, Agile Manifesto, 2001. The above statement from the Agile Manifesto means that executable and functioning products/software/systems are more important than documentation. However, this does not mean that documentation is unimportant and can be omitted completely. An important criterion for documents is therefore that they are needed, especially whether…

Improvement Backlog

The Improvement Backlog describes the supply of improvements and is integrated into the work planning by the relevant organizational unit, self-organized. A rule that describes how much work the organizational unit spends on improvements over time (e.g. 10-20%) helps to keep the predictability of high, especially when Teams are young. The Improvement Backlog is the…

Inspectable Result

Each team organized within the P4 framework produces inspectable results, i.e. all team results can be checked for completeness and quality according to their acceptance criteria and the Definition of Done. The type of inspectable results can vary greatly depending on the type and responsibilities of the team. It is important that the team’s added…