Organizational Levels

Applications & Features

Integrated and tested features are the results of Application Teams .   Common attributes of Teams The minimum requirement for a Team result is that it can be inspected, ie it must be presented in a form that makes it assessable for the Stakeholders (e.g. users of the result). The Definition of Done for the…

Applications and Market Variants

Applications and market versions are integrated, tested and approved products of the organization that can be sold in target markets to customers. They meet the requirements specified as a group from the Stakeholer Needs in the ” feature sets “. These are individually defined in the System Requirements & Functions as well as the Quality…

Application Team & Feature Team

Application Teams use the Modules to build concrete Applications, ie System Variants that are configured for specific markets. The requirements, definition, configuration, integration and testing of the applications are entirely the responsibility of the interdisciplinary Application Teams who also assume system responsibility over the entire product or system life cycle. Some organizations distinguish between Product…

Organizational Artefacts

The Organization is the top level in P4 and organizes the portfolio. For this purpose, the Organization has a Portfolio Backlog with applications as elements, a Portfolio Kanban board and the organization DoD .   Each Organization has the following artifacts: The Oraganizsation’s Structure: It describes the Clusters and Teams within the Organization, as well…

Cluster Artefacts

Each Cluster consists of several teams and divides the Organization into meaningful value streams. He organizes the various systems, applications (products) and markets. For this he has a Cluster Backlog with system versions consisting of features and Modules as elements, a Cluster Kanban board and the Cluster DoD . Each Cluster has the following artifacts:…

Team Artefacts

Teams within the organization are  structured in clusters . All future work of the team will be managed in the Team Backlog . Current work is shown in the Iteration Backlog or on a Kanban board . Depending on the type of team, teams create features and applications , modules and system platforms or services…

Cluster Backlog Item (CBI)

Cluster Backlog Items (CBI) are the individual elements (Backlog Items) of a Cluster Backlog and describe work for a Cluster. The size of  a CBI is initially not limited. It must be small enough in size or devided (refined in the Cluster Backlog Refinement) into several individual items that can be done in one ClusterCycle,…

Cluster Backlog Refinement

Refinement of the Cluster Backlog is viewed as the process of adding details to backlog entries, making estimates, or determining the order of entries in the Cluster Backlog. Refinement is a continuous process in which the Cluster Product Owner and the Team System Engineer Group collectively detail the Cluster Backlog Items. The entries are examined…

Cluster Backlog, Cluster Cycle Backlog and Cluster Kanban

Each Cluster has exactly one Backlog for its area of ​​responsibility and tasks , the Cluster Backlog. In its simplest form, it consists of elements of just one System development that all Teams in the Cluster are working on. In this case, the Cluster Backlog can be referred to as the System Backlog. If the…

Cluster Cycle Transfer within the Inter Cycle Week

The Cluster Cycle  is a kind of large iteration at the Cluster level , it could also be called a “cluster iteration”. A similar cycle is usually also used for the Portfolio level of the entire Organization . The Cycle consists of several Iterations , a preamble consisting of   Cluster Planning and a trailer…