Cluster Backlog, Cluster Cycle Backlog and Cluster Kanban

Each Cluster has exactly one Backlog for its area of ​​responsibility and tasks , the Cluster Backlog. In its simplest form, it consists of elements of just one System development that all Teams in the Cluster are working on. In this case, the Cluster Backlog can be referred to as the System Backlog. If the…

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

Cluster Retrospective

The Cluster Retrospective offers the Cluster Scrum Master (CSM) the opportunity to review the working methods of the cluster, represented by the Cluster Product Owner and the Team System Engineer Group (TSEG) , as well as improvements in the way of working identify and plan for the coming cycle . The Cluster Retrospective takes place…

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

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…

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.

Team Backlog

Team Backlog Each Team has exactly one Backlog for its area of ​​responsibility and tasks . Its elements (Team Backlog Items) consist in the finest level of granularity of Team Goals. The Team Product Owner is  responsible for and prioritizes the Team Backlog. A large part of the Team Backlog is derived by the Team…

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

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…