Team Product Owner

The Team Product Owner prioritizes the Team Backlog and approves the results of the Working Team. The Team Backlog can contain several product developments or parts of them. (A general description of the Product Owner role can be found here …)

Depending on the type and area of responsibility of the Team (“team flavor”), the results of the teams vary greatly. Therefore, the Team Product Owners in P4 can have different names:

Service-Owner

Service owners are the technical leaders of teams who are responsible for an expertise or competence. Often members of such Service Teams are too specialized or too few to be able to work in interdisciplinary teams on a permanent basis. Another reason for a Service Team is that it operates a special infrastructure, e.g. a laboratory. These teams are often a kind of internal service provider within the organization and are usually visited or invited by other teams.

The Service Owner is responsible for prioritizing the service orders of her/his team. In the simplest case, the team uses a Kanban board with a first-come-first-serve principle (FIFO). However, the Service Owner can also divide the services offered by the team into service classes, for example, by means of different service level agreements at different costs.

To achieve an optimal flow of system development, the Service Owner adopts the priorities from the Portfolio Backlog or the Cluster Backlog in the simplest case. In addition, the Service Owner coordinates regularly with the other Team Product Owners within the Team Product Owner Group (TPOG).

Module-Owner

In the development of complex systems there will often be subsystems or Modules to make complexity more manageable (modules encapsulate complexity) or to enable the reuse of Modules and Components by means of a platform or modular concept.

A Module Owner is therefore the manager who ensures that the appropriate Modules are available for application and system development. On the other hand, She/he is responsible for ensuring that the Modules are reusable. Stable interfaces for a platform or modular system are particularly important.

Feature Owner and Application Owner

Feature Owners are the Team Product Owners of interdisciplinary teams who develop and are responsible for one or more Functions (Features) of a system variant (=applications) and make them available to users. Together with the other feature owners and the application owner, the feature owner is responsible for improving the customer value of his Application Team’s product. The application owner is the direct interface to the users of the application to decide on requirements and changes to the application.

Application Owners are the Team Product Owners of the interdisciplinary teams that develop and are responsible for marketable System Variants (=Applications) and make them available to users. The Application Owner is responsible for improving the customer value of the Application Team’s products. The Application Owner is the direct interface to the users and Stakeholders of the application to decide on requirements and changes.

The Application Team with the Application Owner are the internal clients of the Module and Service Teams. Application Teams integrate the Modules provided by the Module Teams with the help of the services provided by the Service Teams.

 

\r\n


Further suitable links:

Events Roles Groups Artifacts
Iteration Planning

Team Sync

Team Backlog Refinement

Team Review

Team Retrospective

Team System Engineer

Team Scrum Master

.

Cluster Product Owner

.

Portfolio Owner

Working Team

.

Team Product Owner Group

Team Backlog

Inspectable Results

Team DoD

Team Improvement Backlog

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 topics within his Team. This can vary significantly depending on the type and area of ​​responsibility.

If a Service Team represents certain expertise (e.g. EMC or acoustics), the Team System Engineer is usually the most experienced of the team.

Within a Module Team , the Team System Engineer knows the modules of his team, their strengths and weaknesses, and their areas of application.

Within an Application Team , the Team System Engineer knows best the technical possibilities for implementing the applications that his team is responsible for.

Within the Working Team, the Team System Engineer has the role of moderating and driving technical decisions and, when in doubt, making them. He is not above the Working Team, but is the “first among equals” (Primus inter paris).

.

\r\n


Further suitable links:

Events Roles Groups Artifacts
Team Planning

Team Sync

Team Backlog Refinement

Team Review

Team Retrospective

Team Product Owner

Team Scrum Master

.

Cluster System Engineer

.

Portfolio Architect

Working Team

Community of Practice

Team Backlog

Inspectable Results

Team DoD

Team Improvement Backlog

 

Practice Lead

Practice leads are professional coaches or trainers within the organization who take care of expertise or technical discipline. They lead a community of practice , train their members and take care of the further development of the topic and the employees within the Organization.

In the transition from classic organizations, the former line managers can become Practice Leads.

.

 

\r\n


Further suitable links:

Events Roles Groups Artifacts
Iteration

.

Cycle

 

Cadence

 

Community of Practice

.

Cluster Management Circle

.

Organisation Management Circle

Practice Backlog

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

 

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