{"id":3992,"date":"2021-02-14T00:12:22","date_gmt":"2021-02-13T23:12:22","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=3992"},"modified":"2021-02-14T00:12:22","modified_gmt":"2021-02-13T23:12:22","slug":"system-engineer","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/system-engineer\/","title":{"rendered":"Responsibility of Technology and Architecture by the System Engineers"},"content":{"rendered":"<p><span style=\"vertical-align: inherit;\">The P4 framework divides its organizational and management structure of product development into three areas:<\/span><\/p>\n<ul>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/marketbusiness\/\"><span style=\"vertical-align: inherit;\">Market and business<\/span><\/a><\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/infrastructureprocesses\/\"><span style=\"vertical-align: inherit;\">Organization, infrastructure and processes<\/span><\/a><\/li>\n<li><span style=\"vertical-align: inherit;\">Technology and architecture<\/span><\/li>\n<\/ul>\n<h2><span style=\"vertical-align: inherit;\">Technology and Architecture<\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\">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: <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/suppliers\/\"><span style=\"vertical-align: inherit;\">suppliers, the supply chain and production<\/span><\/a><span style=\"vertical-align: inherit;\"> .<\/span><\/p>\n<h2><span style=\"vertical-align: inherit;\">The role of the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systemengineer\/\"><span style=\"vertical-align: inherit;\">Team System Engineer<\/span><\/a><\/h2>\n<p><span style=\"vertical-align: inherit;\">Within the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/rteamlevel\/\"><span style=\"vertical-align: inherit;\">Working Team<\/span><\/a><span style=\"vertical-align: inherit;\"> , the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systemengineer\/\"><span style=\"vertical-align: inherit;\">Team System Engineer has<\/span><\/a><span style=\"vertical-align: inherit;\"> the role of moderating and driving technical decisions and, when in doubt, making decisions. He is not &#8220;above&#8221; the Working Team, but is, so to speak, the &#8220;first among equals&#8221; (Primus inter paris).<\/span><\/p>\n<p><span style=\"vertical-align: inherit;\">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.<\/span><\/p>\n<h2><span style=\"vertical-align: inherit;\">The role of the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\"><span style=\"vertical-align: inherit;\">Cluster System Engineer<\/span><\/a><\/h2>\n<p><span style=\"vertical-align: inherit;\">Within the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/sysenggroup\/\"><span style=\"vertical-align: inherit;\">Team System Engineer Group<\/span><\/a><span style=\"vertical-align: inherit;\"> , the Cluster System Engineer has the role of moderating and driving technical decisions and making decisions when in doubt. He is not &#8220;above&#8221; the Team System Engineer Group, but is, so to speak, the &#8220;first among equals&#8221; (Primus inter paris).<\/span><\/p>\n<p><span style=\"vertical-align: inherit;\">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.<\/span><\/p>\n<h2><span style=\"vertical-align: inherit;\">The role of the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioarch\/\"><span style=\"vertical-align: inherit;\">Portfolio architect<\/span><\/a><\/h2>\n<p><span style=\"vertical-align: inherit;\">Within the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/sysarchgroup\/\"><span style=\"vertical-align: inherit;\">Cluster System Engineer Group<\/span><\/a><span style=\"vertical-align: inherit;\"> , the Portfolio architect has the role of moderating and driving technical decisions and, when in doubt, making decisions. He is not &#8220;above&#8221; the Cluster System Engineer Group, but is, so to speak, the &#8220;first among equals&#8221; (Primus inter paris).<\/span><\/p>\n<p><span style=\"vertical-align: inherit;\">The Portfolio architect represents the technical expertise and responsibility of the organization in the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/org-management\/\"><span style=\"vertical-align: inherit;\">organizational management group<\/span><\/a><span style=\"vertical-align: inherit;\"> vis-\u00e0-vis the Portfolio Owner and the organizational Scrum Master in order to achieve a global balance between the topics.<\/span><\/p>\n<p>&nbsp;<\/p>\n<hr \/>\n<p>Further suitable links:<\/p>\n<table  class=\" table table-hover\" >\n<tbody>\n<tr style=\"background-color: #f8f8f8;\">\n<td>Events<\/td>\n<td>Roles<\/td>\n<td>Groups<\/td>\n<td>Artifacts<\/td>\n<\/tr>\n<tr style=\"background-color: #ffffff;\">\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/planning\/\">Team Planning<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/sync\/\">Team Sync<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/refinement\/\">Team Backlog Refinement<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/review\/\">Team Review<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/retrospective\/\">Team Retrospective<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cycleplanning\/\">Cluster Planning<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-sync\/\">Cluster Sync<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterrefinement\/\">Cluster Backlog Refinement<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cyclereview\/\">Cluster Review<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cycleretro\/\">Cluster Retrospective<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolio-planning\/\">Portfolio Planning<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisation-sync\/\">Organisation Sync<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliorefinement\/\">Portfolio Refinement<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolio-review\/\">Portfolio Review<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisations-retrospektive\/\">Organisation Retrospective<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/productowner\/\">Team Product Owner<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systemengineer\/\">System Engineer<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/scrummaster\/\">Team Scrum Master<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\">Cluster Product Owner<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\">Cluster System Engineer<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\">Cluster Scrum Master<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioowner\/\">Portfolio Owner<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioarch\/\">Portfolio Architect<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisationsm\/\">Organisation Scrum Master<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/rteamlevel\/\">Working Team<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cop\/\">Community of Practice<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\">Team Product Owner Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systeminggroup\/\">Team System Engineer Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\">Team Scrum Master Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-management\/\">Cluster Management Circle<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpogroup\/\">Cluster Product Owner Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/sysarchgroup\/\">Cluster System Engineer Group<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"http:\/\/p4dev.hardscrum.com\/csmgroup\/\">Cluster Scrum Master Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/org-management\/\">Organisation Management Circle<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/teambl\/\">Team Backlog<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/ateamlevel\/\">Inspectable Results<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/dod\/\">Team DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/improvementbacklog\/\">Team Improvement Backlog<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterbl\/\">Cluster Backlog<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/usableknowledge\/\">Usable Knowledge<\/a> &amp; <a href=\"http:\/\/p4dev.hardscrum.com\/systemincrement\/\">System Increment<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterdod\/\">Cluster DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterimprovementbacklog\/\">Cluster Improvement Backlog<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliobl\/\">Portfolio Backlog<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioproduct\/\">Systems &amp; Applications<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/applications\/\">System Platforms &amp; Variants<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliodod\/\">Organisation DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioimprovementbacklog\/\">Organisation Improvement Backlog<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"The P4 framework divides its organizational and management structure of product development into three areas: Market and business Organization, infrastructure and processes Technology and architecture Technology and Architecture 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&hellip;","protected":false},"author":3,"featured_media":365,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[24,33],"tags":[],"translation":{"provider":"WPGlobus","version":"2.10.10","language":"en","enabled_languages":["de","en"],"languages":{"de":{"title":true,"content":true,"excerpt":false},"en":{"title":true,"content":true,"excerpt":false}}},"_links":{"self":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/3992"}],"collection":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=3992"}],"version-history":[{"count":3,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/3992\/revisions"}],"predecessor-version":[{"id":3995,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/3992\/revisions\/3995"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/365"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=3992"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=3992"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=3992"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}