Market & Business

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…

Users, Customers and Sales

These are the primary Stakeholders in product development at all levels (Organization , Cluster and Team ). At the Team level, the Application Teams in particular have close contact with Users, Customers and sales, as they give and evaluate the ultimate requirements for the products, systems and applications. Stakeholders are invited to the Review meetings…

Cluster Product Owner (CPO)

Der Cluster-Product-Owner hat mit der Team-Product-Owner-Gruppe auf der Cluster- und System-Ebene die Verantwortung für die Markt- und Geschäftsseite innerhalb des Produktentwicklungsprozesses. (Eine allgemeine Beschreibung des Product-Owner-Rolle befindet sich hier …)

Cluster Product Owner Group (CPOG)

Die Cluster-Product-Owner-Gruppe (CPOG) mit dem Portfolio-Owner hat auf der Portfolio- bzw.  Organisationsebene die Gesamtverantwortung für die Markt- und Geschäftsseite des Produktentstehungsprozesses der Organisation.

Portfolio Backlog, Portfolio Cycle Backlog & Portfolio Kanban

Die oberste Ebene der Backlogs des P4-Frameworks, die Portfolio- und Organisationsebene, beschreibt Applikationen und Marktvarianten der Systeme und Produkte. Jede dieser Varianten wird durch einen Satz von System-Anforderungen (Feature Set) beschrieben.

Portfolio Owner (PFO)

Der Portfolio-Owner ist der Product Owner der Organisation. Er hat zusammen mit der Cluster-Product-Owner-Gruppe (CPOG) auf der Portfolio- bzw.  Organisationsebene die Gesamtverantwortung für die Markt- und Geschäftsseite des Produktentwicklungsprozesses. (Eine allgemeine Beschreibung des Product-Owner-Rolle befindet sich hier …)

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 Product Owner Group (TPOG)

Die Team-Product-Owner-Gruppe besteht aus allen Team-Product-Owner eines Clusters und dem Cluster-Product-Owner. Sie hat auf der Cluster- und System-Ebene die Verantwortung für die Markt- und Geschäftsseite innerhalb des Produktentwicklungsprozesses.

Product Owner is responsible for Market & Business

The P4 framework divides its organizational and management structure of product development into three areas: Market and Business (see below) Organization, infrastructure and processes Technology and Architecture Market and Business The Product Owner roles at the various levels bear responsibility for the products and their markets. In doing so, they communicate with the Stakeholders in…