{"id":440,"date":"2019-07-24T21:34:15","date_gmt":"2019-07-24T19:34:15","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=440"},"modified":"2024-10-02T12:46:01","modified_gmt":"2024-10-02T10:46:01","slug":"cycle","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/cycle\/","title":{"rendered":"Cluster Cycle"},"content":{"rendered":"<p>The basic idea of the <a href=\"http:\/\/p4dev.hardscrum.com\/iteration\/\">Iteration<\/a> as a time-box for the <a href=\"http:\/\/p4dev.hardscrum.com\/rteamlevel\/\">Teams<\/a> is used at Cluster level by the <strong>Cluster Cycle<\/strong> as a larger fixed period as a basic rhythm for the <a href=\"http:\/\/p4dev.hardscrum.com\/rclusterlevel\/\">Cluster<\/a>. Frequently, the <a href=\"http:\/\/p4dev.hardscrum.com\/portfolioproduct\/\">System versions, products and Applications<\/a> are also brought to the market in the rhythm of the Cluster Cycles. The advantage of a fixed rhythm is its predictability for the teams, managers and stakeholders. In practice, a Cluster Cycle length of a quarter of a year has proven itself. There are the following options:<\/p>\n<ul>\n<li>3 four-week iterations + 1 inter Cycle week<\/li>\n<li>4 three-week iterations + 1 inter Cycle week<\/li>\n<li>6 two-week iterations + 1 inter Cycle week<\/li>\n<\/ul>\n<p>This results in 13 weeks per quarter, which corresponds quite accurately to the actual duration (4 x 13 = 52 weeks).<\/p>\n<p>So, one Cluster Cycle consists of:<\/p>\n<ul>\n<li>Cluster Cycle Pre-Planning by the <a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\">Team Product Owner Group (TPOG)<\/a><\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/cycleplanning\/\">Cluster Planning<\/a> (all Teams incl. their POs)<\/li>\n<li>Cluster Cycle Post Planning (again TPOG)<\/li>\n<li>3, 4 or 6 Iterations (of 4, 3 or 2 weeks).During the Iterations:\n<ul>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/sync\/\">Team Sync Meetings<\/a> (Daily Scrums)<\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-sync\/\">Cluster Sync Meetings<\/a> (Scrum-of-Scrums)<\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/organisation-sync\/\">Organization Sync<\/a> (Scrum-of-Scrum-of-Scrums)<\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliorefinement\/\">Portfolio Backlog Refinement<\/a> (by <a href=\"http:\/\/p4dev.hardscrum.com\/clusterpogroup\/\">CPOG<\/a> and <a href=\"http:\/\/p4dev.hardscrum.com\/sysarchgroup\/\">CSEG<\/a>)<\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/clusterrefinement\/\">Cluster Backlog Refinements<\/a> (by <a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\">TPOGs<\/a> and TSEGs)<\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/refinement\/\">Team Backlog Refinements<\/a> (by Working Teams and POs), and<\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/review\/\">Team Reviews<\/a> and <a href=\"http:\/\/p4dev.hardscrum.com\/retrospective\/\">Team Retrospectives<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/cyclereview\/\">Cluster Reviews<\/a> (TPOGs + TSEGs + Stakeholder)<\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/cycleretro\/\">Cluster Retrospectives<\/a> (all Clusters)<\/li>\n<\/ul>\n<p>All Cluster Cycle meetings are held within the <a href=\"http:\/\/p4dev.hardscrum.com\/cycletrans\/\">Inter Cycle Week<\/a>, starting with the Cluster Review and ending with the Cycle Post-Planning.<\/p>\n<h2>Workflow shown as a Sequence Diagramm<\/h2>\n<p>The following UML sequence diagramm shows the sequence of activities of the different roles and groups on cluster and team level for the example of a new feature request:<\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-4859\" src=\"http:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/07\/Cluster_workflow.png\" alt=\"\" width=\"1930\" height=\"1886\" srcset=\"https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/07\/Cluster_workflow.png 1930w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/07\/Cluster_workflow-300x293.png 300w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/07\/Cluster_workflow-1024x1001.png 1024w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/07\/Cluster_workflow-768x750.png 768w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/07\/Cluster_workflow-1536x1501.png 1536w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/07\/Cluster_workflow-60x60.png 60w\" sizes=\"(max-width: 1930px) 100vw, 1930px\" \/><\/p>\n<p><span style=\"color: #ffffff;\">.<\/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\/iteration\/\">Iteration<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/year\/\">Portfolio Cycle<\/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><\/td>\n<td><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\/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\/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","protected":false},"excerpt":{"rendered":"The basic idea of the Iteration as a time-box for the Teams is used at Cluster level by the Cluster Cycle as a larger fixed period as a basic rhythm for the Cluster. Frequently, the System versions, products and Applications are also brought to the market in the rhythm of the Cluster Cycles. The advantage&hellip;","protected":false},"author":3,"featured_media":2021,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[22,5],"tags":[238,256],"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\/440"}],"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=440"}],"version-history":[{"count":34,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/440\/revisions"}],"predecessor-version":[{"id":2706,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/440\/revisions\/2706"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/2021"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=440"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=440"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}