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 Level: Collaboration within the Teams

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