Category: Organizational Levels

Organization Scrum Master (OSM)

Oliver Schönfeld

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 the teams within the Organization  can work optimally across all  clusters . Together with the organization’s  Cluster Scrum Masters  (CSM), he ensures an optimal workflow between the Clusters by solving disabilities and problems that arise in the collaboration of the Clusters. To this end, he organizes and moderates the Organization Retrospective and heads the  Cluster Scrum Master Group , in which the CSMs exchange ideas in order to optimize the working conditions and workflow within the Organization.

.

\r\n

Further suitable links:

Events Roles Groups Artifacts
Portfolio Planning

Organisation Sync

Portfolio Refinement

Portfolio Review

Organisation Retrospective

 Team Scrum Master

.

Cluster Scrum Master

.

Portfolio Owner

Portfolio Architect

 Cluster Product Owner Group

Cluster System Engineer Group

Cluster Scrum Master Group

Organisation Management Circle

 Portfolio Backlog

Systems & Applications

System Platforms & Variants

Organisation DoD

Organisation Improvement Backlog

 

Cluster Scrum Master Group (CSMG)

Oliver Schönfeld

The Cluster Scrum Master Group, consists of the Cluster Scrum Masters of the Clusters and the Organization Scrum Master (OSM)  The group is responsible for the processes, infrastructure and the cultural side of the product development process at the organizational level .

The CSMG maintains the Organization Improvement Backlog to plan and implement improvement projects .

The role of the Organization Scrum Master (OSM) forms the highest management role in the company.

Read More

Team Scrum Master (TSM)

Oliver Schönfeld

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 be solved independently by the self-organized Working Team.

For this purpose, she organizes and moderates the Team Retrospective, in which the team members exchange ideas and experiences in order to strive for an optimum of working conditions and workflow within the team.

The Team Scrum Master works together with other TSMs within the Cluster (Team Scrum Master Group (TSMG) ) to prevent local optimization within the team and to solve problems between teams.

Click here for a general description of the Scrum Master role.

.

\r\n

Further suitable links:

Events Roles Groups Artifacts
Team Planning

Team Sync

Team Backlog Refinement

Team Review

Team Retrospective

 Team Product Owner

Team System Engineer

.

Cluster Scrum Master

.

Organisation Scrum Master

 Working Team

Community of Practice

 Team Backlog

Inspectable Results

Team DoD

Team Improvement Backlog

 

Team Level: Collaboration within the Teams

Oliver Schönfeld

The Team is the basic element of an agile organization and forms the home of employees.

Most of the work takes place in stable and long-lasting Teams. Due to the stability or “longevity”, the teams are available in the event of problems even if the Application or Market Variant is not currently being revised (ie when the classic project teams no longer exist).

P4 adopts the basic structure of a Scrum team. It consists of a Team Product Owner , Team Scrum Master and the Working Team who works together to create value for the Stakeholders. The principle of the separation of powers creates clearly defined areas of role responsibility that complement each other in the Team.

The Team Product Owner is responsible for maximizing the value of the “Product” resulting from the work of the Working Team. How this happens can vary greatly depending on the organization and Working Team, as well as the experts working in them. The Team Product Owner is the only person responsible for managing the Team Backlog.

The Working Team   consists of three to nine members and the Team System Engineer , who work out finished and inspectable results in each Iteration and ideally present a potentially deliverable system or subsystem in the Team Review at the end of the Iteration .

The Team Scrum Master is a “Servant Manager” and is responsible for encouraging and supporting team work in accordance with the Scrum and P4 rules by helping everyone involved to understand the values ​​and practices.

Read More