{"id":5003322,"date":"2015-12-16T23:46:10","date_gmt":"2015-12-17T07:46:10","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=aa_glossary&#038;p=5003322"},"modified":"2022-08-30T11:42:18","modified_gmt":"2022-08-30T18:42:18","slug":"scrum-of-scrums","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/scrum-of-scrums\/","title":{"rendered":"Scrum of Scrums"},"content":{"rendered":"<p>A technique to scale\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/scrum\/\">Scrum\u00a0<\/a>up to large groups (over a dozen people), consisting of dividing the groups into Agile teams of 5-10. Each\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/daily-meeting\/\">daily scrum<\/a> within a sub-team ends by designating one member as an \u201cambassador\u201d to participate in a daily meeting with ambassadors from other teams, called the Scrum of Scrums.<\/p>\n<p>Depending on the context, ambassadors may be technical contributors, <a href=\"https:\/\/agilealliance.org\/glossary\/scrum-master\/\">each team\u2019s Scrum Master<\/a>, or even managers of each team.<\/p>\n<p>The Scrum of Scrums proceeds otherwise as a normal daily meeting, with ambassadors reporting\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/three-qs\/\">completions, next steps, and impediments<\/a>\u00a0on behalf of the teams they represent. Resolution of impediments is expected to focus on the challenges of coordination between the teams; solutions may entail agreeing to interfaces between teams, negotiating responsibility boundaries, etc.<\/p>\n<p>The Scrum of Scrum will track these items via a\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/backlog\/\">backlog<\/a>\u00a0of its own, where each item contributes to improving between-team coordination.<\/p>\n<h2>Also Known As<\/h2>\n<p>Also known as a \u201cMeta Scrum\u201d.<\/p>\n<h2>Origins<\/h2>\n<p>2001: the Scrum of Scrums is first described (summarizing experiences at IDX) in an article by Jeff Sutherland,\u00a0<a href=\"http:\/\/www.controlchaos.com\/storage\/scrum-articles\/Sutherland%20200111%20proof.pdf\">Agile Can Scale: Inventing and Reinventing SCRUM in Five Companies<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A technique to scale Scrum up to large groups (over a dozen people), consisting of dividing the groups into Agile teams of 5-10.<\/p>\n","protected":false},"author":8027401,"featured_media":8067461,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[908],"tags":[],"class_list":["post-5003322","aa_glossary","type-aa_glossary","status-publish","has-post-thumbnail","hentry","category-process"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003322","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/aa_glossary"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/8027401"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=5003322"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003322\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8067461"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=5003322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=5003322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=5003322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}