Roles & Groups

Modelling the organization

With organizational modeling, the specific organization is modeled by P4 elements, i.e. the teams, groups and Clusters are represented by their information and work flows. The processes can now be represented within the organizational model, whereby this is done by defining and documenting the corresponding inputs, responsibilities, actions and outputs. Every  organizational unit is described…

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 Owner (PFO)

The Portfolio Owner is the “Product Owner” of the Organization and has the overall responsibility for the Market and Business side of the product development on the Portfolio / Organizational level, together with the Cluster Product Owner Group (CPOG). (A general description of the Product Owner role can be found here.)   Together with the Portfolio…

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…

Roles, skills, role conflicts & exclusions

Definitions A Role includes the definition of areas of responsibility and corresponding tasks. Persons can take on different roles, possibly several roles. However, not every person can handle several roles at the same time. There are also role conflicts and role exclusions. Skills are personal abilities that combine knowledge, experience and competence. There are certain…

Service Team

Service Teams provide a service or provide their expertises to other teams. There are two types of collaboration with the other teams: Service: Other teams commission the Service Team to visualize and manage their work on a Kanban board Resource provider: Individual members of the Service Team temporarily work as Extended Team members in other…

Stakeholder

Stakeholders are all persons and groups affected by a system, as well as all those directly interested or involved in the product. Stakeholders are invited to Review meetings at all levels and can optionally be invited to Backlog Refinement meetings to explain their requirements. To identify stakeholders, the P4 framework uses two different life cycles…

Team Product Owner (TPO)

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…

Team Product Owner Group (TPOG)

The Team Product Owner Group consists of all Team Product Owners of a Cluster and the Cluster Product Owner . At the Cluster and system level, it is responsible for the Market and Business side  of the product development process. The Team Product Owner Group has the following tasks: Creation of the Cluster 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…