{"id":885,"date":"2019-09-29T16:39:23","date_gmt":"2019-09-29T14:39:23","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=885"},"modified":"2026-03-17T09:52:43","modified_gmt":"2026-03-17T08:52:43","slug":"clusterbl","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/clusterbl\/","title":{"rendered":"Cluster Backlog, Cluster Cycle Backlog and Cluster Kanban"},"content":{"rendered":"<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Each <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/rclusterlevel\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> has exactly one <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/backlog\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Backlog<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> for its area of \u200b\u200bresponsibility and tasks <\/span><span style=\"vertical-align: inherit;\">, the <strong>Cluster Backlog<\/strong>. <\/span><span style=\"vertical-align: inherit;\">In its simplest form, it consists of elements of just one System development that all Teams in the Cluster are working on. <\/span><span style=\"vertical-align: inherit;\">In this case, the Cluster Backlog can be referred to as the System Backlog. <\/span><span style=\"vertical-align: inherit;\">If the Cluster is responsible for several systems, all backlog elements of the different systems are contained within the Cluster Backlog.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Product Owner Group<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> is<\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> responsible for and prioritizes the <\/span><span style=\"vertical-align: inherit;\">Cluster Backlog <\/span><span style=\"vertical-align: inherit;\">.<\/span><span style=\"vertical-align: inherit;\">The Team Product Owner Group consists of all <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/productowner\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Product Owners <\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">of the Cluster<\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">\u00a0and the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Product Owners<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">. <\/span><span style=\"vertical-align: inherit;\">A large part of the Cluster Backlog is derived by the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpogroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Product Owner Group<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/sysarchgroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster System Engineer Group<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> from the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliobl\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio Backlog<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> by refinement in the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliorefinement\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio Backlog Refinements<\/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;\">The other part of the Cluster Backlog consists of work and measures that the Cluster carries out to improve the quality of work and results, e.g.<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Quality measures and improvement of the Cluster process (ie the <a href=\"http:\/\/p4dev.hardscrum.com\/clusterimprovementbacklog\/\">Cluster Improvement Backlog<\/a>)<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Maintenance of the products, systems and Modules responsible for the cluster<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Maintenance and servicing of tools.<\/span><\/span><\/li>\n<\/ul>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In order to make the working speed of the Clusters more predictable, the proportion of backlog items <\/span><span style=\"vertical-align: inherit;\">derived <\/span><span style=\"vertical-align: inherit;\">from the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliobl\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio Backlog<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> should be relatively stable over time.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The Cluster Backlog is prioritized by the Cluster Product Owner.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/clusterrefinement\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Backlog Refinement<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> , the Cluster Backlog Items are presented by the Cluster Product Owner and <\/span><span style=\"vertical-align: inherit;\">estimated <\/span><span style=\"vertical-align: inherit;\">by the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/sysenggroup\/\"><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;\">. <\/span><span style=\"vertical-align: inherit;\">Since this consists of members of all Teams in the Cluster, this group is best suited for this.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/cycleplanning\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Planning,<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> \u00a0the TSEG pulls as many Cluster Backlog Items into the <a href=\"http:\/\/p4dev.hardscrum.com\/cycle\/\">Cycle<\/a> as the TSEG believes due to the previous working speed of the cluster. <\/span><span style=\"vertical-align: inherit;\">This is the Cycle Backlog that represents the plan for the next cycle.<\/span><\/span><\/p>\n<h2><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Work in cycles or in continuous Kanban mode<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Clusters have the choice of planning, executing and controlling their work in a rhythm of fixed time units, ie in Cycles, or in a continuous flow, with each Backlog item individually going through the different states of the work process of the Cluster. <\/span><span style=\"vertical-align: inherit;\">This is made transparent on a Kanban board.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">A Cluster chooses between Cycle-mode and Kanban-mode, depending on the product and how planning and approval are carried out. <\/span><span style=\"vertical-align: inherit;\">With a regular release rhythm, for example every three months, work in Cycles is recommended.<\/span><\/span><\/p>\n<h2><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Cycle Backlog<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The Cycle Backlog reflects the work of a Cluster for a currently running <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/cycle\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cycle<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> . <\/span><span style=\"vertical-align: inherit;\">The estimated work, ie backlog elements, is pulled into the Cycle Backlog by the TSEG at the beginning of the Cycle (pull) and thus scheduled for the next Cycle (forecast).<\/span><\/span><\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-medium wp-image-1452\" src=\"http:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/iteration-backlog-300x300.png\" alt=\"\" width=\"300\" height=\"300\" srcset=\"https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/iteration-backlog-300x300.png 300w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/iteration-backlog-150x150.png 150w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/iteration-backlog-768x768.png 768w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/iteration-backlog-1024x1024.png 1024w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/iteration-backlog-60x60.png 60w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/iteration-backlog.png 1182w\" sizes=\"(max-width: 300px) 100vw, 300px\" \/><\/p>\n<h2><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Kanban<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">If the Cluster works in Kanban-mode, it uses a Cluster Kanban Board instead of the Cycle Backlog. <\/span><span style=\"vertical-align: inherit;\">The first column corresponds to the Cluster Backlog and the last column to the status &#8220;Done&#8221;. <\/span><span style=\"vertical-align: inherit;\">All other columns are defined by the Team Scrum Master Group of the cluster, according to the internal Cluster work process.<\/span><\/span><\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-medium wp-image-1458\" src=\"http:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/kanban-board-300x300.png\" alt=\"\" width=\"300\" height=\"300\" srcset=\"https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/kanban-board-300x300.png 300w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/kanban-board-150x150.png 150w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/kanban-board-768x768.png 768w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/kanban-board-1024x1024.png 1024w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/kanban-board-60x60.png 60w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/kanban-board.png 1182w\" sizes=\"(max-width: 300px) 100vw, 300px\" \/><\/p>\n<h3>Example of a Cluster Kanban Board<\/h3>\n<p>The board shown below displays all the work from a Cluster of three teams. The orange and yellow cards represent work on a <a href=\"https:\/\/p4dev.hardscrum.com\/applications\/\">Product variant<\/a>. The green cards are <a href=\"https:\/\/p4dev.hardscrum.com\/systemreq\/\">Features <\/a>and <a href=\"https:\/\/p4dev.hardscrum.com\/architecture\/\">Product capabilities<\/a>. The blue backlog item cards represent the work of the three teams.<\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone wp-image-5255 size-large\" src=\"http:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/cluster-board-1024x609.png\" alt=\"\" width=\"648\" height=\"385\" srcset=\"https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/cluster-board-1024x609.png 1024w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/cluster-board-300x178.png 300w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/cluster-board-768x456.png 768w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/cluster-board-1536x913.png 1536w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/09\/cluster-board-2048x1217.png 2048w\" sizes=\"(max-width: 648px) 100vw, 648px\" \/><\/p>\n<p><span style=\"color: #ffffff;\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">.<\/span><\/span><\/span><\/p>\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\/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><\/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\/teambl\/\">Team Backlog<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/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><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"Each Cluster has exactly one Backlog for its area of \u200b\u200bresponsibility and tasks , the Cluster Backlog. In its simplest form, it consists of elements of just one System development that all Teams in the Cluster are working on. In this case, the Cluster Backlog can be referred to as the System Backlog. If the&hellip;","protected":false},"author":3,"featured_media":1457,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[20,22],"tags":[351,348,375,9,363],"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\/885"}],"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=885"}],"version-history":[{"count":24,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/885\/revisions"}],"predecessor-version":[{"id":2256,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/885\/revisions\/2256"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/1457"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=885"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=885"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=885"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}