Organizational Levels

Portfolio Planning

Planning at the Portfolio level is a semi-continuous process in the P4 framework, just like budget planning, for example, which is closely linked to Portfolio Planning. The planning process consists of the preparation through the Portfolio refinement and the Portfolio Planning event. The planning process takes place at the level of the Portfolio Backlog elements.…

Portfolio Review

At the end of each Portfolio Cycle, a Portfolio Review is held in which the Cluster System Engineer Group (CSEG) and the Portfolio Owner (PFO) present the results to the Stakeholders. They receive feedback from the Stakeholders on the results so that the Portfolio Owner can adjust the Portfolio Backlog if necessary . Along with any…

Practice Lead

Practice leads are professional coaches or trainers within the organization who take care of expertise or technical discipline. They lead a community of practice , train their members and take care of the further development of the topic and the employees within the Organization. In the transition from classic organizations, the former line managers can…

Products, Applications and Market Variants

The Portfolio Backlog at the Organizational level, the top level of all Backlogs, contains Systems, Products and Application variants, as well as product variants for special markets. Each of these product variants is described by a set of System Requirements (feature set). In this way, the product variants can be estimated against each other with…

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.…

Personal Scrum

In the P4 framework, people work together in teams that are as stable as possible, with the vast majority of people belonging to exactly one team (also known as a nucleus). These teams have a common responsibility and the team members work on common goals. To do this, they exchange information with each other, complement…

Service Team

Service Teams provide a service or provide their expertises to other teams. There are two types of collaboration with the other teams: Service: Other teams commission the Service Team to visualize and manage their work on a Kanban board Resource provider: Individual members of the Service Team temporarily work as Extended Team members in other…

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, System Architecture & Capabilities

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…