{"id":263,"date":"2019-07-14T17:43:14","date_gmt":"2019-07-14T15:43:14","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=263"},"modified":"2024-05-17T12:56:12","modified_gmt":"2024-05-17T10:56:12","slug":"rclusterlevel","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/rclusterlevel\/","title":{"rendered":"Cluster"},"content":{"rendered":"<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Each Cluster consists of several <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/rteamlevel\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Teams<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and divides the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/rportfoliolevel\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Organization<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> into related and consistent Value Streams. <\/span><span style=\"vertical-align: inherit;\">The <\/span><span style=\"vertical-align: inherit;\">Clusters are responsible for the <\/span><span style=\"vertical-align: inherit;\">various <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/application\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Systems, Applications and Products for specific Markets<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> .<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Many different competencies are usually required for the implementation of extensive and complex systems. <\/span><span style=\"vertical-align: inherit;\">In order to work together on such a project, a single Working Team with a maximum of 10 people is usually not enough. <\/span><span style=\"vertical-align: inherit;\">The cooperation between the Teams has to be regulated and areas of responsibility have to be defined. <\/span><span style=\"vertical-align: inherit;\">To achieve this, teams are brought together in a higher-level organizational unit. <\/span><span style=\"vertical-align: inherit;\">This overarching organizational unit is called the P4 framework <\/span><\/span><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster<\/span><\/span><\/strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> . <\/span><span style=\"vertical-align: inherit;\">A Cluster has system responsibility for one or more related systems (or products), for a product area, a platform or large module.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">By scaling the Scrum roles to the Cluster level, there are &#8230;<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">a <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systemownergroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Product Owner (CPO)<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> representing the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/productowner\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Product Owner<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> ( <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">TPOG<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> ),<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">a <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster System Engineer<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systeminggroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team System Engineer Group (TSEG)<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> as representatives of the Working Teams of the Cluster and<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">a <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/clusterSM\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Scrum Master<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> representing the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/scrummaster\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Scrum Master<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> ( <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">TSMG<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> )<\/span><\/span><\/li>\n<\/ul>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The three roles of <a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\">Cluster Product Owner<\/a>, the <a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\">Cluster Scrum Master<\/a> and the <a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\">Cluster System Engineer<\/a> form the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-management\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Management Circle of the Cluster<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> (see also the next paragraph).<\/span><\/span><\/p>\n<h2><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Roles &amp; groups<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In order to organize the cooperation, in addition to the Teams, various groups are formed that regulate the three different areas of responsibility. <\/span><span style=\"vertical-align: inherit;\">The groups are formed on the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/p4-principles#ueberlappung\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">principle of overlap<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> from members of the Working Teams. <\/span><span style=\"vertical-align: inherit;\">In order to clearly regulate this dual affiliation, the working hours for working in the group are determined centrally. <\/span><span style=\"vertical-align: inherit;\">From the outset there is a clear agreement on when and how long the group will work together (<\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/kadenz-cadence\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cadence<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">).<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">There are the following groups according to the three areas of responsibility:<\/span><\/span><\/p>\n<ol>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Market and Business: The <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systemownergroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Product Owner Group (TPOG)<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> with the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Product Owner (CPO)<\/span><\/span><\/a><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Technology and architecture: the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systeminggroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team System Engineer Group (TSEG)<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> with the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster System Engineer (CSE)<\/span><\/span><\/a><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Processes, infrastructure and culture: the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Scrum Master Group (TSMG)<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> with the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/clusterSM\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Scrum Master (CSM)<\/span><\/span><\/a><\/li>\n<\/ol>\n<h2><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-management\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Management Circle<\/span><\/span><\/a><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The <a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\">Cluster Product Owner<\/a>, the <a href=\"http:\/\/CSE\">Cluster System Engineer<\/a> and the <a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\">Cluster Scrum Master<\/a> form the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-management\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Management Circle<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">\u00a0following the <a href=\"http:\/\/p4dev.hardscrum.com\/p4-principles#gewaltenteilung\">principal of separating powers<\/a>. <\/span><span style=\"vertical-align: inherit;\">They support and complement each other in the decision-making of topics that reach their level or have been escalated to them by one of the three groups. According to the <a href=\"http:\/\/p4dev.hardscrum.com\/p4-principles#local-decision\">principle of local decision-making<\/a>, most decisions are made at the Cluster or Team level and only a small proportion escalate. <\/span><span style=\"vertical-align: inherit;\">These constructs effectively prevents &#8220;lonely individual manger decisions&#8221;, because decisions are previously examined and discussed from all three directions, and thus effectively balanced.<\/span><\/span><\/p>\n<p>The Cluster Management Circle forms an interdisciplinary group of managers who, like all other groups and teams, hold daily or weekly Sync meetings and Retrospectives.<\/p>\n<h2>Team Setups und Team Collaboration Models<\/h2>\n<p><span style=\"vertical-align: inherit;\">Teams that work within the Cluster often deliver partial results and intermediate products to each other. <\/span>To make this transparent for everyone, the Team Setup describes which people work in which Team and how the teams work together. The following options are available for this:<\/p>\n<ul>\n<li>A Team <span style=\"text-decoration: underline;\">receives an artifact<\/span> as a supply (Knowledge, work results, Samples or Modules)<\/li>\n<li>A Team <span style=\"text-decoration: underline;\">receives a service<\/span>\u00a0(e.g. an EMC or acoustic measurement)<\/li>\n<li>A Service\/Expert team <span style=\"text-decoration: underline;\">lends a person to another team<\/span> for some Iterations (full-time at the Nucleus or part-time as Extended Team Member)<\/li>\n<li>Two or three teams <span style=\"text-decoration: underline;\">share Extended Team members<\/span><\/li>\n<li>Two closely cooperating Teams can collaborate in the following ways (e.g. two Feature Teams working on the same Application or two Module Teams working against a complex technical interface)\n<ul>\n<li>They pull their <a href=\"http:\/\/p4dev.hardscrum.com\/team-iteration-backlog\/\">Team Iteration Backlog<\/a> from the same <a href=\"http:\/\/p4dev.hardscrum.com\/teambl\/\">Team Backlog<\/a> and may have the same <a href=\"http:\/\/p4dev.hardscrum.com\/productowner\/\">Team Product Owner<\/a>,<\/li>\n<li>You have a <a href=\"http:\/\/p4dev.hardscrum.com\/sync\/\">Joint Team Sync<\/a> one or more times per week,<\/li>\n<li>They do the <a href=\"http:\/\/p4dev.hardscrum.com\/planning\/\">Team Planning<\/a>, the <a href=\"http:\/\/p4dev.hardscrum.com\/refinement\/\">Team Backlog Refinement<\/a>, the <a href=\"http:\/\/p4dev.hardscrum.com\/review\/\">Team Review<\/a> and\/or the <a href=\"http:\/\/p4dev.hardscrum.com\/retrospective\/\">Team Retrospective<\/a> together.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>The collaboration model between two teams can be discussed and agreed in a playful way with the <a href=\"https:\/\/p4dev.hardscrum.com\/team-collaboration-poker\/\">Team Collaboration Poker<\/a>.<\/p>\n<h2><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Workflows &amp; Value Streams<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Value Stream Maps describe the different areas of responsibility and delivery objects. <\/span><span style=\"vertical-align: inherit;\">For this purpose, the P4 framework uses the SIPOC description from classic organizational development. <\/span><span style=\"vertical-align: inherit;\">(Supplier &gt;&gt; Input &gt;&gt; Process &gt;&gt; Output &gt;&gt; Customer).<\/span><\/span><\/p>\n<h3>Example Value Stream<\/h3>\n<p>[WPinclude]example-medium-size-organization[\/WPinclude]<\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">See also: <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/aclusterlevel\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Artifacts of the cluster<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/iteration\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">events of the Cluster during the iteration<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and &#8221; <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/cycletrans\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The Cycle change: events between the cycles<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> &#8220;.<\/span><\/span><\/p>\n<p><span style=\"color: #ffffff;\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">.<\/span><\/span><\/span><\/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\/cycleplanning\/\"><span style=\"color: #333333;\">Cluster Planning<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-sync\/\"><span style=\"color: #333333;\">Cluster Sync<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterrefinement\/\"><span style=\"color: #333333;\">Cluster Backlog Refinement<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cyclereview\/\"><span style=\"color: #333333;\">Cluster Review<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cycleretro\/\"><span style=\"color: #333333;\">Cluster Retrospective<\/span><\/a><\/td>\n<td>&nbsp;<\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\"><span style=\"color: #333333;\">Cluster Product Owner<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\"><span style=\"color: #333333;\">Cluster System Engineer<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\"><span style=\"color: #333333;\">Cluster Scrum Master<\/span><\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioowner\/\"><span style=\"color: #333333;\">Portfolio Owner<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioarch\/\"><span style=\"color: #333333;\">Portfolio Architect<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisationsm\/\"><span style=\"color: #333333;\">Organisation Scrum Master<\/span><\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\"><span style=\"color: #333333;\">Team Product Owner Group<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systeminggroup\/\"><span style=\"color: #333333;\">Team System Engineer Group<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\"><span style=\"color: #333333;\">Team Scrum Master Group<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-management\/\"><span style=\"color: #333333;\">Cluster Management Circle<\/span><\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/clusterbl\/\"><span style=\"color: #333333;\">Cluster Backlog<\/span><\/a><\/p>\n<p><span style=\"color: #333333;\"><a href=\"http:\/\/p4dev.hardscrum.com\/usableknowledge\/\">Usable Knowledge<\/a> &amp; <a href=\"http:\/\/p4dev.hardscrum.com\/systemincrement\/\">System Increment<\/a><\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterdod\/\"><span style=\"color: #333333;\">Cluster DoD<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterimprovementbacklog\/\"><span style=\"color: #333333;\">Cluster Improvement Backlog<\/span><\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"Each Cluster consists of several Teams and divides the Organization into related and consistent Value Streams. The Clusters are responsible for the various Systems, Applications and Products for specific Markets . Many different competencies are usually required for the implementation of extensive and complex systems. In order to work together on such a project, a&hellip;","protected":false},"author":3,"featured_media":355,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[22,3],"tags":[199],"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\/263"}],"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=263"}],"version-history":[{"count":49,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/263\/revisions"}],"predecessor-version":[{"id":2252,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/263\/revisions\/2252"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/355"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=263"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=263"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=263"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}