Organizational Levels

Organization Management Circle (OMC)

The Organization is managed by a group of managers, the Organization Management Circle (OMC) The Portfolio Owner, the Portfolio Architect and the Organization Scrum Master form the Organization Management Circle (OMC). They support and complement each other in the decision-making of topics that reach their level or have been escalated to them by one of…

Cluster Management Circle

A Cluster within the product development Organization is managed by a group of managers. The Cluster Product Owner, the Cluster System Engineer and the Cluster Scrum Master form the Cluster Management Circle following the principal of separating powers. They support and complement each other in the decision-making of topics that reach their level or have been…

Module Team

Module Teams are responsible for versioned Modules, Components or Platforms. Complex systems are usually divided into System Elements or Modules as sub-units. Platforms are often used, in which the Modules form the basic building blocks for combining and creating System Variants and Applications. Often you will find specific competencies in Module Teams that are only…

Usable Knowledge & Documented Decisions

Usable and documented knowledge is the basis of any system development. It makes it possible to make conscious design decisions. Usable Knowledge also represents the first stage of reuse (see principles). At a higher level, however, they also represens knowledge of the possibilities and limitations of integrated system solutions (Limits and Trade-offs). To achieve this,…

Organization Scrum Master (OSM)

The Organization Scrum Master is part of the  Cluster Scrum Master Group  and is responsible for the  infrastructure and processes  at the  organizational level  , ie the entire product development. The Organization Scrum Master forms  the  management of the entire Organization together with the  Portfolio architect  and the  Portfolio Owner . The OSM ensures that…

Organization

The Organization represents the top level in product development and operations, and thus all people, roles and groups. It is also called the Portfolio Level. All of the Organization’s work is shown in the Portfolio Backlog with the greatest possible transparency.   Larger Organizations (over 100-150 people) are divided into different sub-organizations, which are called…

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

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…