Areas

Organization Retrospective

The Organization Retrospective offers the Organization Scrum Master (OSM) the opportunity to review the working methods of the organization, represented by the Portfolio Owner (PFO) and the Cluster System Engineer Group (CSEG) , as well as improvements to the Identify and plan how to work for the coming cycle . The Organization Retrospective takes place…

P4-Ops

P4-Ops describes the Operation of an organization. It is divided into the following areas: Product Management, Sales and Marketing Supply chain (purchasing, production, shipping Application Engineering, Service, Support/Hotline, Trainings Infrastructure Services (IT, HR, accounting and site management)   The P4-Ops framework is sufficient for organizations without product development. In combination with the P4-Dev Framework, which…

Portfolio Architect (PFA)

With the Cluster System Engineer Group at Portfolio and organizational level, the Portfolio architect is responsible for the technology and architecture side of the entire product development process. The Portfolio architect forms the management of the entire Organization together with the Portfolio Owner and the Organization Scrum Master .   Together with the Portfolio architect,…

Portfolio Backlog, Portfolio Cycle Backlog & Portfolio Kanban

The top level of the Backlogs of the P4 framework, the Portfolio and Organizational level , describes all Applications and market variants of the Systems and Products to be develped in the entire Organization. Each of these variants is described by a set of System Requirements (feature set). In this way, the Application, systems &…

Portfolio Owner (PFO)

The Portfolio Owner is the “Product Owner” of the Organization and has the overall responsibility for the Market and Business side of the product development on the Portfolio / Organizational level, together with the Cluster Product Owner Group (CPOG). (A general description of the Product Owner role can be found here.)   Together with the Portfolio…

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…

Team 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 predictability of other Backlog Items high. The Improvement Backlog is the planning and structuring tool of the…

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

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