Areas

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? What are the responsibilities…

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

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

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…

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…