{"id":1276,"date":"2019-10-15T23:06:37","date_gmt":"2019-10-15T21:06:37","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=1276"},"modified":"2020-05-12T14:12:28","modified_gmt":"2020-05-12T12:12:28","slug":"organisation-sync","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/organisation-sync\/","title":{"rendered":"Organisation Sync"},"content":{"rendered":"<h3><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Organizational Sync (Scrum-of-Scrums-of-Scrums)<\/span><\/span><\/h3>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">This event enables several Clusters to communicate with each other in order to coordinate dependencies, disruptions, new findings and decisions, etc. during ongoing work. <\/span><span style=\"vertical-align: inherit;\">The Clusters themselves decide how often this is needed (e.g. daily, weekly).<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The representatives of the Cluster can be the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster System Engineers <\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">of<\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> the Clusters. <\/span><span style=\"vertical-align: inherit;\">However, other technical representatives of the Cluster can also be designated.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The Organization Sync takes place (usually in a semicircle) in front of the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliobl\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio Kanban Board of the Organization<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> , since the members move the Portfolio Backlog Items in the Organization Sync.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The three questions in Organization Sync are:<\/span><\/span><\/p>\n<ol>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">What has my Cluster been doing since the last Organization Sync?<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">What is my Cluster expected to do until the next Organization Sync?<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Where is my Cluster blocked and needs support?<\/span><\/span><\/li>\n<\/ol>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In a similar way, the structure of the Organization Sync can also be used for the exchange of certain roles or expertise, e.g. a sync of the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Scrum Masters<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> , 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;\"> , the testers, the designers, designers, etc. of a Cluster .<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Due to the shortness of a maximum of 15 minutes, the Organization Sync is only suitable for identifying problems, but not for discussing or solving them. <\/span><span style=\"vertical-align: inherit;\">The required members can use the time after the Organization Sync to discuss problems, while the unnecessary members can continue to work.<\/span><\/span><\/p>\n<h4><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Organizational sync visitors<\/span><\/span><\/h4>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Visitors who want to experience the Organization Sync can participate with the permission of the members. <\/span><span style=\"vertical-align: inherit;\">The visitors are in the second row and only listen, unless they are addressed by an active member. <\/span><span style=\"vertical-align: inherit;\">Visitors can be:<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioowner\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio Owner<\/span><\/span><\/a><\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/stakeholder\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Stakeholders<\/span><\/span><\/a><\/li>\n<\/ul>\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\/sync\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Sync<\/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\/cluster-sync\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Sync<\/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\/portfolio-planning\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio Planning<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliorefinement\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio refinement<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolio-review\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio Review<\/span><\/span><\/a><\/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\/portfolioowner\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio Owner<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioarch\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio Architect<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisationsm\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Organization Scrum Master<\/span><\/span><\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpogroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Product Owner Group<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/sysarchgroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster System Engineer Group<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/csmgroup\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster Scrum Master Group<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/org-management\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Organization Management Circle<\/span><\/span><\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliobl\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Portfolio Backlog<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioproduct\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Systems &amp; Applications<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/applications\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">System Platforms &amp; Variants<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliodod\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Organization DoD<\/span><\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioimprovementbacklog\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Organization Improvement Backlog<\/span><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"Organizational Sync (Scrum-of-Scrums-of-Scrums) This event enables several Clusters to communicate with each other in order to coordinate dependencies, disruptions, new findings and decisions, etc. during ongoing work. The Clusters themselves decide how often this is needed (e.g. daily, weekly). The representatives of the Cluster can be the Cluster System Engineers of the Clusters. However, other&hellip;","protected":false},"author":3,"featured_media":1427,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[5,23],"tags":[152],"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\/1276"}],"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=1276"}],"version-history":[{"count":17,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1276\/revisions"}],"predecessor-version":[{"id":2537,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1276\/revisions\/2537"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/1427"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=1276"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=1276"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=1276"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}