Cluster Level

Integrated System Sample (System increments)

System increments are partial or full integrations of system versions that are verified by internal or external tests and (depending on the degree of regulation) by user or market tests. System increments are often created at cluster level, i.e. by integrating sub-products from the various Teams in a Cluster. For the System increment, P4 has…

Cluster Management Circle

A Cluster within the product development Organization is managed by a group of managers. The Cluster Product Owner, the Cluster System Engineer and the Cluster Scrum Master form the Cluster Management Circle following the principal of separating powers. They support and complement each other in the decision-making of topics that reach their level or have been…

Usable Knowledge & Documented Decisions

Usable and documented knowledge is the basis of any system development. It makes it possible to make conscious design decisions. Usable Knowledge also represents the first stage of reuse (see principles). At a higher level, however, they also represens knowledge of the possibilities and limitations of integrated system solutions (Limits and Trade-offs). To achieve this,…

Samples & Integrations (Backlog Item Type)

Samples & Integrations represent all work that is required to develop, build and test prototype samples (whether virtual or physical). These Samples can be concepts, simulations, prototypical partial assemblies, virtual prototypes, rapid prototypes, up to pre-series samples, which may be tested in user studies. Samples & Integrations are created  to close Knowledge Gaps through learning.…

System Requirements & Functions

Systems are described at the top level by System Requirements and Functions (features). Requirements only describe abilities or properties in the “problem area”, so they are still independent of concrete system solutions. The solution space is already limited by the Quality Attributes & Constraints . Interfaces to neighboring systems in the environment and their properties…

System Increment

System increments are partial or full integrations of system versions that are verified by internal or external tests, as well as by user and / or market tests. System increments are mostly created by the Application teams of the Cluster i.e. by integrating partial results of the different teams of a cluster (module and platform…

System Concepts & Capabilities, Solution Options

System concepts describe possible solutions for system and product variants (applications = feature sets) and their requirements . System concepts implement the System Requirements within the restrictions (contraints) and balance the quality requirements (Quality Attributes)out. The P4 framework explicitly provides several System Concepts as solution options for the implementation of System Requirements in the system…

Team Product Owner Group (TPOG)

The Team Product Owner Group consists of all Team Product Owners of a Cluster and the Cluster Product Owner . At the Cluster and system level, it is responsible for the Market and Business side  of the product development process. The Team Product Owner Group has the following tasks: Creation of the Cluster Backlog ,…

Team Scrum Master Group (TSMG)

The Team Scrum Master Group with the Cluster Scrum Master (CSM) has responsibility at the Cluster and System level for the  product development process, the infrastructure and the cultural aspects .   Together with the Cluster Scrum Master (CSM) , the Team Scrum Master Group has the following tasks: Creating and optimizing the team setup as…

Team System Engineering Group (TSEG)

The Team System Engineer Group is made up of all Team System Engineers of the Custer. At the Cluster level, it corresponds to the role of the Working Team. The Team System Engineer Group with the Cluster System Engineer is responsible for the Technology & Architecture within the product development at the Cluster / System…