Areas

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

Team Retrospective

The Team Retrospective gives the team the opportunity to review themselves and to identify and plan improvements in the way they work for the upcoming iteration . It takes place between the Team Review and the next Team Planning. For a four-week iteration, an upper limit of three hours is set. The meeting is usually…

Team Scrum Master (TSM)

Team Scrum Master (TSM) The TSM ensures that the members of his Team can work optimally. He ensures an optimal work flow between the team members, by discovering improvements and solving disabilities and problems (presented managed in the Team Improvement Backlog) that arise in the cooperation of the teams. This especially concerns those that cannot…

Team Scrum Master Group (TSMG)

Die Team-Scrum-Master-Gruppe mit dem Cluster-Scrum-Master (CSM) hat, auf der Cluster- und System-Ebene, die Verantwortung für den Produktentstehungsprozess, die Infrastruktur und die kulturellen Aspekte.

Team System Engineer (TSE)

The Team System Engineer represents the technical expertise and responsibility of his Team in the Team System Engineer Group of the Cluster . If the team does not agree on any other regulation, he also represents the Team in the Cluster Syncs (scrum-of-scrums) . For this, he should have the broadest possible knowledge of the…