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 .
With the Team System Engineer Group at the Cluster / system level, the cluster System Engineer is responsible for the technology and architecture within the product creation process.
The P4 framework divides its organizational and management structure of product development into three areas:
The technical roles of the different levels are responsible for the used and new technologies, as well as the architecture of the developed systems, i.e. the breakdown into Functions, Modules, Components and interfaces. They communicate with the stakeholders in this area: suppliers, the supply chain and production .
Within the Working Team , the Team System Engineer has the role of moderating and driving technical decisions and, when in doubt, making decisions. He is not “above” the Working Team, but is, so to speak, the “first among equals” (Primus inter paris).
The Team System Engineer of a team represents the technical expertise and responsibility of his team in groups and committees, as well as in the coordination between the teams. As a representative of its Working Team, it estimates, for example, the Cluster Backlog Items together with the Team System Engineers of the other teams in the cluster.
Within the Team System Engineer Group , the Cluster System Engineer has the role of moderating and driving technical decisions and making decisions when in doubt. He is not “above” the Team System Engineer Group, but is, so to speak, the “first among equals” (Primus inter paris).
The Cluster System Engineer of a Cluster represents the technical expertise and responsibility of its cluster, in groups and committees, as well as in the coordination between the Clusters. As a representative of its Team System Engineer Group, it estimates, for example, the Portfolio Backlog entries together with the Cluster System Engineers of the other Clusters.
Within the Cluster System Engineer Group , the Portfolio architect has the role of moderating and driving technical decisions and, when in doubt, making decisions. He is not “above” the Cluster System Engineer Group, but is, so to speak, the “first among equals” (Primus inter paris).
The Portfolio architect represents the technical expertise and responsibility of the organization in the organizational management group vis-à-vis the Portfolio Owner and the organizational Scrum Master in order to achieve a global balance between the topics.
\r\n
Further suitable links:
| Events | Roles | Groups | Artifacts |
| Team Planning
. . |
Team Product Owner
. . |
Working Team
. . |
Team Backlog
. Usable Knowledge & System Increment . |
The Cluster System Engineer Group (CSEG) consists of the Cluster System Engineers of all Clusters in the Organization . At the organizational level, it corresponds to the role of the Working Team at the team level.
Together with the Portfolio Architect , the Cluster System Engineer Group is responsible for the Technology and Architecture side of the product development process at the organizational and portfolio level .
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 Product Owner
. . |
Working Team | Team Backlog |
The Team System Engineer Group is made up of all Team System Engineers from the cluster . At the Cluster level, it corresponds to the role of the Working Team.
The Team System Engineer Group with the Cluster System Engineer is responsible for the technology and architecture within the product development at the Cluster / system level .
Suppliers are important external Stakeholders of product development at all levels (Organization , Cluster and Team ) and supply chain and production are important internal Stakeholders. At the Team level, the Module Teams in particular, have close contact with suppliers because they provide important boundary conditions for the technology.
Stakeholders are invited to the review events on all levels, to give feedback to the relevant organizational units. These can be Team Reviews of the teams, Cluster Reviews of the Clusters or Portfolio Reviews .
Stakeholders can be invited to refinement meetings to clarify requirements. These can be Team Backlog Refinements , Cluster Backlog Refinements or Portfolio refinements .
.
Suitable and further articles:
| Events | Roles | Groups | Arteacts |
| Team Backlog Refinement
. . |
Team Product Owner
. . |
Working team
. Management circle of the cluster . |
Team Backlog
. Usable Knowledge & system increment . |