SCRUM 111 e1595254269752

Scrum of Scrums for Scaled Agile: Make It Work

It is becoming more and more evident that the true potential of Agile lies in large companies and scaled approaches. The State of Agile report in 2020 revealed that Scrum this year is more common than in previous years. It is now the most commonly deployed framework for addressing development issues. 75% of survey respondents practice Scrum or a hybrid technique incorporating it. But what can you gain from implementing Scrum of Scrums and how to do it right? 

One of the most popular ways to scale Agile today is Scrum of Scrums. And while many companies have adopted this practice already, we thought it might be interesting for others to know just how exactly it works.  

What is Scrum of Scrums? 

Scrum of Scrums
A member per Scrum team is delegated to participate in Scrum of Scrums

Scrum of Scrums has been originally defined by Jeff Sutherland. It is a technique to scale Scrum up to large groups (over a dozen people) and involves dividing the groups into Agile teams of 5-10 people.  

Sutherland has been quoted as saying the three distinguishing factors between Scrum teams and normal teams are self-management, continuity of team membership and dedication to a single project. As well as claiming that Scrum should run with software architecture.

According to Sutherland, the main purpose of Scrum of Scrums is to deliver working software of all teams to the Definition of Done at the end of the Sprint.  To make sure this happens, the Scrum of Scrums Master is accountable and has to be able to ensure that all the processes function.  

How does it work?  

The original Agile speaks of a small team and its management. However, when we think of a large organization we usually have a team of a few hundred or even a few thousand people. As a result, having stand-ups or one project board for all of those people will be nearly impossible. Luckily, the Scrum of Scrums approach gives a way to work around that. 

Scrum of Scrums does not look at the organization as a one big team. Instead, it asks to divide people into small teams of up to 10 people based on their function and product features. This way, we are no longer looking at a room of a few hundred people and have small manageable teams instead. The traditional Scrum roles of Product Owner, Scrum Master and others are retained in every single team. All teams plan and complete their work independently from each other relying on the Scrum methodology.  

Scrum system
Scrum system, source: Habr

How is the process coordinated in Scrum of Scrums? 

To coordinate the overall vision between the teams, a new meeting by the name of Scrum of Scrums comes about. It takes place every day, two times a week or once a week at minimum. That happens after the daily stand-ups and one member per team has to attend and represent. The flow of this meeting is similar to a daily stand-up. Just instead of presenting what they have personally worked on, the delegates are representing their team’s progress. They report completions, next steps and impediments on behalf of the teams they represent. 

However, the Scrum of Scrums meeting should NOT be a status report. The goal is rather to make sure the individual teams make their sprint goals. As well as that the overall project goal of all teams is met.

 Discussion and resolution of problems during Scrum of Scrums has to focus on the coordination between the teams. Solutions may entail agreeing to interfaces between teams, negotiating responsibility boundaries, etc. The Scrum of Scrums Master coordinates this meeting and decides where the project should go next. Thus giving direction for individual teams and making sure they stay on track.  

This method is sure to help you manage time better.

Agile maturity test

Scaled Agile adoption and challenges according to 2020 State of Agile Report 

According to State of Agile Report from year 2020, 95 percent of questioned organizations have some form of agile process in place. However, practice maturity and adoption are still a work in progress.  

For example, 77 percent of businesses are following standard Scrum rituals, including stand-ups, retrospectives, sprint planning and reviews. But only around 50 percent are adopting agile transformation practices such as roadmaps, release planning and agile estimation.  

About one-third of respondents are applying the Scaled Agile Framework. Roughly another third are using other scaling frameworks, mostly Scrum of Scrums.  

There appear to be several common challenges to scaling agile. These include: resistance to change, lack of leadership board’s participation, inconsistent processes and chaotic organization. As well as being unable to live up to agile values, insufficient management support and lack of training.  

Scaling methodologies aim to get more people adopting a semi-standard agile practice, but the approach often fails to address organizational culture and people’s mindsets. The aforementioned symptoms are all signals that organizations are fighting cultural and not scaling issues. 

Scaled Agile approaches in use, , 14th Annual State of Agile Report
Scaled Agile approaches in use in 2020, 14th Annual State of Agile Report

How can you implement Scrum of Scrums to scale Agile successfully? 

It takes time to find the right groove and learn how to coordinate all the teams in Scrum of Scrums. However, to make it easier, here are a few tricks to put you on the right track. 

  • To make sure teams understand each other and their responsibilities, it is good to have the same key roles in all of the teams. Depending on your project, it may be Product Owner, Coach, Architect or something else. Making sure to have the same key roles in all the teams will create clarity and easy structure to follow, eliminating most of the novelty confusion. 
  • Another tip is to schedule all  team sprints to start and end at the same time. Teams might be able to do more or less depending on their velocity, but having the iterations aligned will allow for easier planning and predictable releases right off the bat. 
  • Lastly, remember that you can still continue to scale upwards when needed. This is especially true for large products or companies when the Scrum of Scrums still has more than 10 people in attendance and is becoming long and ineffective. Instead, divide this meeting into 2 or more Scrum of Scrums and add a third level meeting that would contain representatives from each of the second level Scrum of Scrums.  This will improve productivity and allow for easier management of the project. 

In conclusion, the Scrum of Scrums is a quite simple way to scale Agile in your organization and take advantage of its benefits. But as with any scaling approach, first you should make sure that it is right for you and then look into the best practices to ensure you stay on track. 

Teamhood is a hyper visual project and team management solution that helps companies to streamline business processes and deliver results faster. Teamhood is designed for professional teams seeking efficiency at work and full empowerment of their talents. Teamhood provides workspaces, customized boards with fine-tuned time tracking, collaboration functionalities as well as visual agile metrics reporting.
Teamhood is developed by Eylean, a project management software company since 2011. Eylean products are valued by its numerous customers globally such as Mercedes AG, Festool, Johnson&Johnson, Rabobank and others.

© 2020 Teamhood ® by Eylean. All rights reserved. We use cookies on our website.

Teamhood uses cookies to improve your experience, personalize content and ads, to provide social media features and to analyze our website‘s traffic. By agreeing you accept the use of Cookies in accordance with our Cookie Policy.