Organization Level

Organization DoD

The teams of all Clusters in the organization , the Cluster System Engineer Group , the Cluster Product Owner Group and the stakeholders must understand what it means when a backlog entry or a result is referred to as “done”. Although the Cluster DoDs can differ significantly from Cluster to cluster, there is only one…

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

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

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…

Organisation Sync

Organizational Sync (Scrum-of-Scrums-of-Scrums) This event enables several Clusters to communicate with each other in order to coordinate dependencies, disruptions, new findings and decisions, etc. during ongoing work. The Clusters themselves decide how often this is needed (e.g. daily, weekly). The representatives of the Cluster can be the Cluster System Engineers of the Clusters. However, other…

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 Item (PFBI)

Portfolio Backlog Items (PFBI) are the individual elements (Backlog Items) of a Portfolio Backlog and describe work for the entire Organization. The size of  a PFBI is initially not limited. It must be small enough in size or devided (refined in the Portfolio Backlog Refinement) into several individual items that can be done in one…

Portfolio Backlog Refinement

Refinement of the Portfolio Backlog is the process of creating new backlog items, adding details to backlog items, making estimates, splitting backlog items, or changing the order of items in the Portfolio Backlog. Refinement is a continuous process in which the Portfolio Owner and the Cluster System Engineer Group (CSEG) jointly detail the Portfolio Backlog…

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 Cycle

The basic idea of the Iteration as a time-box for the Teams is used at Organization level by the Portfolio Cycle as a larger fixed period as a basic rhythm for the Organization. Frequently, the System versions, products and Applications are also brought to the market in the rhythm of the Portfolio Cycles. The advantage of…