{"id":1831,"date":"2019-12-31T15:09:18","date_gmt":"2019-12-31T14:09:18","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=1831"},"modified":"2026-02-02T12:10:26","modified_gmt":"2026-02-02T11:10:26","slug":"cycleretro","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/cycleretro\/","title":{"rendered":"Cluster Retrospective"},"content":{"rendered":"<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The Cluster Retrospective offers 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><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> the opportunity <\/span><span style=\"vertical-align: inherit;\">to review <\/span><span style=\"vertical-align: inherit;\">the working methods of the cluster, represented by the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Product Owner<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and 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;\"> , as well as improvements in the way of working <\/span><span style=\"vertical-align: inherit;\">identify and plan <\/span><span style=\"vertical-align: inherit;\">for the coming <\/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 Cluster Retrospective takes place between the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/zyklus-review-cycle-review\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Review<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and the next <\/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;\"> and is based on the results of the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/retrospective\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Retrospectives of the teams<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> , mostly from the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Scrum Master Group<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">were processed. <\/span><span style=\"vertical-align: inherit;\">An upper limit of four hours is set for this for a quarterly cycle. <\/span><span style=\"vertical-align: inherit;\">The meeting is usually shorter for shorter cycles. <\/span><span style=\"vertical-align: inherit;\">The CSM ensures that the meeting takes place and that all participants understand its purpose. <\/span><span style=\"vertical-align: inherit;\">The CSM ensures that the meeting is constructive and productive and teaches everyone to stick to the time frame (time box). <\/span><span style=\"vertical-align: inherit;\">Due to its responsibility for the P4 process, the CSM takes part in the Cluster Retrospective as an equal member. <\/span><span style=\"vertical-align: inherit;\">It is carried out to &#8230;<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">to review how the past Cycle was in terms of the teams, relationships, processes, infrastructure and tools involved;<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">identify the most important and possible improvements and put them in order; <\/span><span style=\"vertical-align: inherit;\">and<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">prepare a plan for implementing improvements to the way the Cluster works.<\/span><\/span><\/li>\n<\/ul>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The Team Scrum Master Group is working to improve the cluster&#8217;s development processes and practices so that the cluster&#8217;s teams can work more effectively and satisfactorily in the coming cycle. <\/span><span style=\"vertical-align: inherit;\">In each Cluster Retrospective, the Team Scrum Master Group works out ways to improve result quality by adapting the processes accordingly or by defining-of-done, provided these changes are appropriate and do not conflict with product or company standards. <\/span><span style=\"vertical-align: inherit;\">At the end of the Cluster Retrospective, the TSMG should have identified improvements for the coming cycle.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In the Cluster Retrospective, the Team Scrum Master Group also checks the workflows between the teams (e.g. using value stream mapping) and adjusts the areas of responsibility of the teams and, if necessary, also the team structures within the Cluster .<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The Team Scrum Masters take the suggestions and measures with them into their teams.<\/span><\/span><\/p>\n<h3><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Process of the Cluster Retrospective<\/span><\/span><\/h3>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Mostly, the Team Scrum Masters bring problems, impediments and improvements from their teams with them to the TSMG, which they have collected in the Team Retrospectives of the teams. <\/span><span style=\"vertical-align: inherit;\">These are collected and prioritized in the Cluster Improvement Backlog. <\/span><span style=\"vertical-align: inherit;\">During the working hours of TSMG, the highest priority improvements are analyzed and processed during the current cycle. <\/span><span style=\"vertical-align: inherit;\">In the Cluster Retrospective, changes are then jointly decided and implemented.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">For the determination of further problems, disabilities and ideas for improvement at the Cluster level, the TSMG uses the same methodological approaches and questions as at the team level, e.g.<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Glad, Sad, Mad<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Keep, change, puzzled<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Good, problems, questions<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Start, stop, keep, more, less<\/span><\/span><\/li>\n<\/ul>\n<p>The <a href=\"http:\/\/p4dev.hardscrum.com\/delegation-poker\/\">Delegation Poker game<\/a> is particularly suitable for negotiating the delegation of responsibility to the TSEG.<\/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><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Further suitable links:<\/span><\/span><\/p>\n<table  class=\" table table-hover\" >\n<tbody>\n<tr>\n<td><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Events<\/span><\/span><\/td>\n<td><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Roles<\/span><\/span><\/td>\n<td><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Groups<\/span><\/span><\/td>\n<td><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Artifacts<\/span><\/span><\/td>\n<\/tr>\n<tr>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/retrospective\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Retrospective<\/span><\/span><\/a><\/p>\n<p><span style=\"color: #ffffff;\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">.<\/span><\/span><\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cycleplanning\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster planning<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-sync\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Sync<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterrefinement\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Backlog Refinement<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cyclereview\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Review<\/span><\/span><\/a><\/p>\n<p><span style=\"color: #ffffff;\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">.<\/span><\/span><\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisations-retrospektive\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Organization retrospective<\/span><\/span><\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Product Owner<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster System Engineer<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Scrum Master<\/span><\/span><\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Product Owner Group<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systeminggroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team System Engineer Group<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Scrum Master Group<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-management\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Management Circle<\/span><\/span><\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/clusterbl\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Backlog<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/usableknowledge\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Usable Knowledge<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> &amp; <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systemincrement\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">System Increment<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterdod\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster DoD<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterimprovementbacklog\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Improvement Backlog<\/span><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"The Cluster Retrospective offers the Cluster Scrum Master (CSM) the opportunity to review the working methods of the cluster, represented by the Cluster Product Owner and the Team System Engineer Group (TSEG) , as well as improvements in the way of working identify and plan for the coming cycle . The Cluster Retrospective takes place&hellip;","protected":false},"author":3,"featured_media":1891,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[22,5,34],"tags":[269,306,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\/1831"}],"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=1831"}],"version-history":[{"count":26,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1831\/revisions"}],"predecessor-version":[{"id":2173,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1831\/revisions\/2173"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/1891"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=1831"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=1831"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=1831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}