{"id":197,"date":"2021-04-08T10:18:15","date_gmt":"2021-04-08T07:18:15","guid":{"rendered":"https:\/\/hygger.io\/guides\/?p=197"},"modified":"2021-10-22T18:55:03","modified_gmt":"2021-10-22T15:55:03","slug":"scrum-of-scrums","status":"publish","type":"post","link":"https:\/\/hygger.io\/guides\/agile\/scrum\/scrum-of-scrums\/","title":{"rendered":"Scrum of Scrums"},"content":{"rendered":"

One of the essential characteristics of\u00a0<\/span>Scrum<\/span><\/a>\u00a0is the suggested size of the team. If you want your\u00a0<\/span>Scrum team<\/span><\/a>\u00a0to collaborate efficiently, it is better to have up to 9-10 people working together. However, there are many cases when an organization is large and it has multiple cross-functional departments that work on product development.<\/span><\/p>\n

They may have even 50 or 100 employees working together who are distributed over offices, cities, or even countries. Is it easy to establish proper communication between the multiple teams? When a Scrum team becomes too large, the most appropriate solution is to form more teams. These teams may work with their own\u00a0<\/span>sprint<\/span><\/a>\u00a0backlogs and hold their own daily meetings. In order to keep everybody on the same page, a\u00a0<\/span>Scrum of Scrum<\/span><\/strong>\u00a0meeting takes place between these teams.<\/span>\"Scrum<\/p>\n

How does Scrum of Scrums work? What are the secrets of running an effective Scrum of Scrums meeting? In this post, we are trying to figure it out.<\/p>\n

What Is Scrum of Scrums?<\/span><\/h2>\n

Scrum of Scrums is an approach proposed by the Agile methodology aimed to connect multiple teams that need to work together to deliver complex solutions. With the help of this technique, Agile teams can develop and deliver products through inspection, transparency, and adaptation, at scale.<\/span><\/p>\n

Scrum of Scrums looks especially successful when all high-performing Scrum team members perform towards a common goal, have respect and trust. Meta-Scrum is simply another name of this technique.<\/span><\/p>\n

Team sizing is critical here. It is recommended to have 4-6 people in a team. Too small or too large groups of people might struggle with the delivery of complex products.<\/span><\/p>\n

Splitting a large team into smaller ones will help you to develop personal relationships and maintain desired outcomes. However, be careful when splitting teams, as it is rather important to balance skills across the teams and thoroughly break down work duties.<\/span><\/p>\n

New bottlenecks and unexpected dependencies may always occur that will lead to the slowing down of delivery. Professional prioritization of improvement stories and a strong focus on\u00a0<\/span>retrospective meetings<\/span><\/a>\u00a0will help you to overcome these challenges.<\/span><\/p>\n

When you strive for creating multiple teams to deliver a common objective, you will definitely need strong coordination. This is where the Scrum of Scrums concept comes to the rescue.<\/span><\/p>\n

Scrum of Scrums: What Are the Origins?<\/span><\/h3>\n

The Scrum of Scrums conception was first introduced by IDX Systems (GE Healthcare now). The authors, Jeff Sutherland and Ken Schwaber implemented this technique to scale individual Scrum teams to the enterprise level (in 8 business units, each with multiple product lines).<\/span><\/p>\n

Every product line had its Scrum of Scrums, some products had multiple Scrum of Scrums. All products had to be delivered to the market, having a release cycle of three months or less and had to be integrated and deployed every six months to support regional healthcare providers.<\/span><\/p>\n

Then the technique was used at the patient keeper to support the multiple enterprise releases to both hospital systems and partners every sprint. A typical Scrum of Scrums meeting lasted about 15 minutes every day.<\/span><\/p>\n

What Is the Purpose of the Scrum of Scrums Concept?<\/span><\/h3>\n

A Scrum of Scrums is a virtual team that includes delegates with embedded links to the originating teams. In comparison with any typical organizational hierarchy, these interlinking team structures can significantly reduce communication paths. The main purpose is to coordinate small and independent teams.<\/span><\/p>\n

Teams that perform in accordance with the Scrum of Scrums concept not only coordinate delivery but also ensure a fully integrated product at the end of each Sprint. So, Scrum of Scrums works as a release team that delivers value to clients. Companies usually apply this approach as an initial step to scale Agile and practice the delivery of more complex products.<\/span><\/p>\n

What Is the Usual Agenda of a Scrum of Scrums Meeting?<\/span><\/h3>\n

The following questions should be covered during the event:<\/span><\/p>\n