{"id":458,"date":"2019-07-25T23:15:47","date_gmt":"2019-07-25T21:15:47","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=458"},"modified":"2023-11-05T16:28:16","modified_gmt":"2023-11-05T15:28:16","slug":"cluster-sync","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/cluster-sync\/","title":{"rendered":"Cluster Sync (Scrum-of-Scrums)"},"content":{"rendered":"

Cluster Sync (scrum-of-scrums)<\/span><\/span><\/h3>\n

This event enables multiple <\/span><\/span>Working Teams<\/span><\/span><\/a> to communicate with each other in order to coordinate dependencies, disruptions, new findings and decisions, etc. with one another during ongoing work. <\/span>The teams decide how often this is needed (e.g. daily or weekly). Depending on the context, there can be different types of Cluster Syncs, e.g. a daily coordination of all testers of the interdisciplinary teams in a cluster. The Team Product Owners, Team System Engineers and the TSMs should also have a regular coordination round for their groups.<\/span><\/span><\/p>\n

The team representatives can be the <\/span><\/span>Team System Engineers<\/span><\/span><\/a> of<\/span><\/span> the teams. <\/span>However, other technical representatives of the teams can also be appointed.<\/span><\/span><\/p>\n

The Cluster Sync takes place (usually in a semicircle) in front of the <\/span><\/span>Cluster Kanban Board<\/span><\/span><\/a> because the members move the Cluster Backlog Items in the Cluster Sync.<\/span><\/span><\/p>\n

The three questions in Cluster Sync are:<\/span><\/span><\/p>\n

    \n
  1. What has my team done since the last Cluster Sync?<\/span><\/span><\/li>\n
  2. What will my team expect to do until the next Cluster Sync?<\/span><\/span><\/li>\n
  3. Where is my team blocked and needs support?<\/span><\/span><\/li>\n<\/ol>\n

    The structure of the Cluster Sync can also be used for the exchange of certain roles or expertise, for example a Cluster Sync of the <\/span><\/span>Team Scrum Masters<\/span><\/span><\/a> , the Team Product Owners, the testers, the designers, designers, etc.<\/span><\/span><\/p>\n

    Due to the shortness of a maximum of 15 minutes, the Cluster Sync is only suitable for identifying problems, but not for discussing or solving them. <\/span>The required members can use the time after the Cluster Sync to discuss problems, while the unnecessary members can continue to work.<\/span><\/span><\/p>\n

    Visitors in Cluster Sync<\/span><\/span><\/h4>\n

    Visitors who want to experience the Cluster Sync can participate with the permission of the members. <\/span>The visitors are in the second row and only listen, unless they are addressed by an active member. <\/span>Visitors can be:<\/span><\/span><\/p>\n