{"id":1651,"date":"2019-12-28T18:43:29","date_gmt":"2019-12-28T17:43:29","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=1651"},"modified":"2024-05-17T12:55:16","modified_gmt":"2024-05-17T10:55:16","slug":"clusterpo","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/clusterpo\/","title":{"rendered":"Cluster Product Owner (CPO)"},"content":{"rendered":"<p>The Cluster Product Owner is part of the <a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\">Team Product Owner Group (TPOG)<\/a>. They have the responsibility for the <a href=\"http:\/\/p4dev.hardscrum.com\/marketbusiness\/\">market and business side<\/a> of the product development process at the <a href=\"http:\/\/p4dev.hardscrum.com\/rclusterlevel\/\">Cluster and System level<\/a>. (A general description of the product owner role can be found <a href=\"http:\/\/p4dev.hardscrum.com\/marketbusiness\/\">here<\/a>.)<\/p>\n<p>The <span style=\"font-size: 16px;\">Cluster-Product-Owner,<\/span> the <a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\">Cluster System Engineer<\/a> and the <a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\">Cluster Scrum Master<\/a> form the <a href=\"http:\/\/p4dev.hardscrum.com\/cluster-management\/\">Management Circle of the Cluster<\/a>.<\/p>\n<p>The Cluster Product Owner has the following tasks (together with the Team Product Owner Group):<\/p>\n<ul>\n<li>Managing the <a href=\"http:\/\/p4dev.hardscrum.com\/clusterbl\/\">Cluster Backlog<\/a>, derived from the <a href=\"http:\/\/p4dev.hardscrum.com\/portfoliobl\/\">Portfolio Backlog<\/a>, in coordination with the <a href=\"http:\/\/p4dev.hardscrum.com\/sysenggroup\/\">Team System Engineer Group (TSEG)<\/a><\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliobl\/\">Requirements management: Receiving <\/a><a href=\"http:\/\/p4dev.hardscrum.com\/systemreq\/\">requests\/requirements about systems, applications &amp; features<\/a>, and working with the <a href=\"http:\/\/p4dev.hardscrum.com\/stakeholder\/\">Stakeholders<\/a> on the requirements\n<ul>\n<li>Secure the <a href=\"http:\/\/p4dev.hardscrum.com\/definition-of-ready\/\">DoR<\/a> so that the System Engineer Group can analyze and estimate it<\/li>\n<li>Refinement of Systems, Applications &amp; Features and distribution Backlog Items to <a href=\"http:\/\/p4dev.hardscrum.com\/teambl\/\">Team Backlogs<\/a>.<\/li>\n<li>Analyzing Systems, Applications &amp; Features regarding the business value, e.g. by using <a href=\"http:\/\/p4dev.hardscrum.com\/planning-poker\/\">Planning-Poker<\/a> and relative &#8220;Value Points&#8221;.<\/li>\n<\/ul>\n<\/li>\n<li>Prioritizing systems, applications &amp; features within the Cluster Backlog. The Cluster Backlog is freely available and transparent for all Stakeholders<\/li>\n<li>Release management (planning, acceptance and release)\n<ul>\n<li>Release planning: Planning of the systems, applications &amp; features in reasonable System Variants and versions. The release planning is publicly available and transparent for all stakeholders<\/li>\n<li>Feedback of the priority and, if necessary, scheduling information to the stakeholders<\/li>\n<\/ul>\n<\/li>\n<li>Optional, especially if the organization is not continuously agile: Information &amp; Reporting: Display progress and allow updating of higher-level plans<\/li>\n<li>Definition &amp; maintenance of processes and templates (self-organisation)\n<ul>\n<li>Cluster Kanban Board<\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/nabc\/\">NABC<\/a>, <a href=\"http:\/\/p4dev.hardscrum.com\/lbc\/\">Lightweight Business Case<\/a>.<\/li>\n<li>Templates for <a href=\"http:\/\/p4dev.hardscrum.com\/stakeholderstory\/\">User Stories<\/a> and <a href=\"http:\/\/p4dev.hardscrum.com\/usecase\/\">Use Cases<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<hr \/>\n<p>Further suitable links:<\/p>\n<table  class=\" table table-hover\" >\n<tbody>\n<tr>\n<td>Events<\/td>\n<td>Roles<\/td>\n<td>Groups<\/td>\n<td>Artifacts<\/td>\n<\/tr>\n<tr>\n<td><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><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/productowner\/\">Team Product Owner<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/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><\/td>\n<td><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><\/td>\n<td><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><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"The Cluster Product Owner is part of the Team Product Owner Group (TPOG). They have the responsibility for the market and business side of the product development process at the Cluster and System level. (A general description of the product owner role can be found here.) The Cluster-Product-Owner, the Cluster System Engineer and the Cluster&hellip;","protected":false},"author":3,"featured_media":370,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[22,32,24],"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\/1651"}],"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=1651"}],"version-history":[{"count":13,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1651\/revisions"}],"predecessor-version":[{"id":2221,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1651\/revisions\/2221"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/370"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=1651"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=1651"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=1651"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}