Agile
min read

Guide to Scrum of Scrums: An Answer to Large-Scale Agile

Check how Scrum of Scrums can help your organization become more agile.
Mitul Makadia
Mitul Makadia
Updated on Jan 12
Agile
min read
Guide to Scrum of Scrums: An Answer to Large-Scale Agile
Check how Scrum of Scrums can help your organization become more agile.
image
Mitul Makadia
Updated on Oct 03
Table of contents
History of Scrum of Scrums(SoS)
What is Scrum of Scrums?
How does SOS work?
Purpose of Scrum of Scrums
Structure of the Scrum of Scrums
Benefits of a Scrum of Scrums
Scrum of Scrums Best Practices 
Who Attends Scrum of Scrums?
Frequency of Meeting 
Agenda of Scrum of Scrums
Conclusion

The number of people on your team can significantly impact your business. When you’re starting your business initially, it’s easy to keep track of everything that needs to be done. But as the team grows, things can get out of hand. 

Hey there! This blog is almost about 2600+ words long & not everyone likes to read that much.

We understand that.This is precisely why we made a podcast on the topic. Mitul Makadia, CEO & Founder of Maruti Techlabs, talks to Bikshita Bhattacharyya about his Agile implementation, strategy, and process during the nascent stages of the company.

He walks us through the challenges he faced, how the business benefited from scaling Agile, and how important is the scrum master in making Agile a success at the organizational level. Here is a small snippet from that episode. Check it out!
 

At the same time, if multiple teams work parallel on one product, they need to communicate regularly and effectively. In most cases, people across many teams will not collaborate closely or even see each other regularly, so how can they communicate efficiently? How can they divide work between them if they don’t meet each other face-to-face?

For decades, the Scrum Guide has proven to be a helpful resource in supporting teams and companies that need to address these issues. Scrum is a framework for developing products, which embraces empiricism and is optimized for complex projects. 

Here’s when the Scrum of Scrums technique comes to play. Scrum of Scrums is the process of managing multiple Scrum-based projects of any size as an integrated and unified business process. As Scrum is one of the most popular agile frameworks, it requires a unique set of capabilities and a shift in thinking for everyone involved. 

Scrum of Scrums refers to a customer and project management technique that utilizes concurrent development rather than serial. It provides a lightweight way to manage the interactions between several scrum teams across the organization. 

This guide will study the working, structure, and benefits of a scrum of scrum practices in detail to help you scale and integrate your work with multiple Scrum teams working on the same project. 

History of Scrum of Scrums(SoS)

The Scrum of Scrums framework was first introduced by Jeff Sutherland and Ken Schwaber in 1996 while operating at the Lawrence Livermore National Laboratory. The original purpose of this framework was to coordinate the activities of eight business units with multiple product lines per business unit in a single development cycle. 

Sutherland and Schwaber found that having separate scrum teams for each business unit impeded workflow within and across business units, so they experimented. They gathered all eight product teams into a single room. They had their work together by forming a meta-team or “Scrum of Scrums” to create an environment where independent teams could synchronize their efforts more efficiently.

Later, in 2001, Sutherland published this experience under the title “Agile Can Scale: Inventing and Reinventing SCRUM in Five Companies,” which mentioned Scrum of scrums for the first time. 

What is Scrum of Scrums?

Scrum of Scrums is designed to be a lightweight solution for scaling agile methods. The main benefit of the Scrum of Scrums approach is to provide a way to enhance communication by connecting people from different Scrum teams who need to collaborate and coordinate with each other. 

The essential Scrum of Scrums’ purpose is that multiple teams are working on a single product, and there needs to be a way for all of these teams to communicate with each other. 

It’s particularly relevant for organizations with teams across geographies and time zones because it provides a means for teams to synchronize their work, communicate any issues or delays, and coordinate planning activities. 

According to the definition of Jeff Sutherland, “Scrum of scrums as I have used it is responsible for delivering the working software of all teams to the Definition of Done at the end of the Sprint, or for releases during the sprint.”

A Scrum of Scrums (SoS) is a meeting between two sprints, where the development team discusses their inter-team dependencies. The scaled agile framework is run by the development team members, who are best positioned to discuss inter-team dependencies and find a solution.

Scrum of Scrums helps deploy and deliver complex products by adapting transparency and inspection at a large scale. It enables scrum teams to work towards common goals and complete the project by aligning. 

Participants present at the Scrum of Scrums answer similar questions like daily Scrum. For instance:

  • What has been the team’s progress since we last met?
  • What problems are the team facing, and can the other teams resolve them?
  • What tasks will the team carry out before the next meet?

There are various techniques by which you can implement the Scrum of Scrums. It could be a meeting within the team or with all teams. Therefore, scrum of scrum definition aims to get all teams in sync with each other so that any dependencies between teams have been identified and resolved.

How does SOS work?

Scrum of Scrums divides a large team into smaller scrum teams or subteams. Each subteam will have its daily standups, sprint planning sessions, and other events as part of a Scrum of Scrums meetings. 

The basic idea is to give each subteam the autonomy to plan their work independently while still coordinating with the rest of the team—just as independent teams do in a traditional scrum. Here, the large number of people divided into smaller scrum teams can include up to 10 members in each team. 

Each team chooses one developer to act as spokesperson, often known as “ambassador” for daily standups during their scaled Scrum. Another role is the Scrum of Scrums master, similar to the Scrum Master for Scrum methodology but at a higher level. 

Purpose of Scrum of Scrums

A Scrum of Scrums meeting can be a valuable way to communicate with organizations with different goals. Here’s how:

  • Organizations use this approach as the initial step to scale agile and organize the delivery of large, complex products.
  • The Scrum of Scrums supports the agile teams by enhancing their productivity and coordinating their work with other teams.
  • When problems arise in one part of a system, they can affect the rest of the system directly and indirectly. Scrum of Scrums provides an effective way to identify these issues and address them on time.
  • Through this meeting, representatives from each team can share updates about their progress and report on issues that may have arisen.
  • Scrum of Scrum meetings helps ensure that tasks are synchronized, and team members are kept up to date with the work remaining on their project.
  • Scrum-of-Scrum teams not only coordinate delivery but ensure a fully integrated product at the end of every sprint.
  • Scrum meetings are also helpful for solving problems and making decisions. 
  • This meeting helps ensure transparency by providing everyone with the latest information on the project.

guide to scrums of scrums

Structure of the Scrum of Scrums

structure of scrum of scrums

A Scrum of Scrums team is a cross-functional team that includes representatives from multiple Scrum teams. It follows the same practices and events as an individual Scrum team, and each member of the Scrum of Scrums team has the same role as a member of the corresponding Scrum team. However, to deploy the potentially integrated product at the end of every sprint, new additional roles are included here, not found in Scrum teams. 

For instance, there is the quality assurance leader in every Scrum of Scrums team. The quality assurance leader is responsible for overseeing, testing, and maintaining the quality of the final product at the end of each sprint. 

Another such role is Scrum of Scrums Master, who is responsible for focusing on the progress and product backlogs, facilitating prioritization, and continuously improving the effectiveness of Scrum of Scrums. 

These roles take up the 15 minutes of scaled daily Scrum meet-ups to align and improve the impediments of the project. Here, each team’s product owner or ambassador discusses each team’s requirements, risks, and sprint goals with the other team. It also identifies the improvements of their team that other groups can leverage to achieve the final product. 

Benefits of a Scrum of Scrums

Benefits-of-a-Scrum-of-Scrums

All this discussion about Scrum of Scrums meetings has brought up an important question: What are the benefits of the Scrum of Scrums approach? Let’s try to answer this question in detail below:

  • Scrum of Scrums enables you to streamline the cross-team collaboration between different teams working on the same project. 
  • SoS is more accessible for large enterprises to handle and deal with at a large scale.
  • It helps to spread the information to individual Scrum teams via their representative. Hence, every team is informed about the current and to-be-achieved details of the project. 
  • SoS meetings encourage a better decision-making process, which reduces the conflict among the team members regarding the project. 
  • It makes the problem-solving process easier by discussing the issues and difficulties faced by any team. 
  • Scrum of Scrums reinforces each team’s role, preventing them from drifting apart from project goals and putting them back on track. 
  • It provides a way to handle new and unforeseen development problems that can affect multiple parts of the project and the team in the future. 

scrum best practices

Scrum of Scrums Best Practices 

Scrum of Scrums is the best way to scale agile to organizations with multiple teams. As for the Scrum of Scrums( SoS) meeting agenda, below are some of the SoS best practices to consider for getting the team composition right and conducting an effective meeting: 

  • Establish the length and frequency of every meeting ahead of time. Schedule to meet, not more than twice a week, with the time frame of regular scrum meetings, i.e., 15-30 minutes, tops. 
  • Set aside time to address problems and prevent them from becoming a roadblock. 
  • Track the progress of ongoing and finished scaled daily Scrum.
  • Encourage transparency between your team and establish a positive environment to create a collective agreement on the definition of “complete.”
  • Make sure each team is prepared to share its progress points in the meeting.
  • Deliver stories that depend on other teams early in the sprint so you can build in time to discover and address issues they might uncover.
  • Prepare and track a timeline for the team’s demo meeting.
  • Make sure the meeting attendees represent each team. Selecting the appropriate people will ensure a productive meeting.
  • Remember that Scrum meetings are not the same as status meetings. Status meetings are a holdover from waterfall methodology and have no place in agile practice.
  • Instruct each attendee to report back to their team about the meeting. If people don’t know why they are attending, what good are these meetings?

Who Attends Scrum of Scrums?

The Scrum of Scrums Meeting is not prescribed by an official description, as it depends on the theme of the sprint. For example, if the theme is user experience, one team can send an expert in this area. The teams can send different experts depending on the Sprint theme; however, one rule applies: nine people can be there in the end.

Although sending a Scrum master to a Scrum of Scrum meeting makes sense, shipping a product owner or development team member with more excellent technical knowledge might be even better. The Scrum of Scrum representative may change over time as issues arise.

The Scrum of Scrums can continue at higher levels as well. Meetings can occur not only among teams but also between experts, for instance, between two product owners, to discuss the feasibility of their product towards the market condition. It is not uncommon for this meeting to be called a “Scrum of Scrum of Scrums,” but this designation is not always used.

Frequency of Meeting 

The team itself should decide the frequency of this meeting. According to Ken Schwaber, the sessions should happen daily and last no longer than 15 minutes. However, a Scrum team may discover that it does not need to meet as often as initially planned.

It is more effective to schedule meetings less frequently yet for more extended periods. You can do it by holding two or three sessions a week instead of daily encounters. It allows team members to focus on any issues that may arise, rather than addressing them in the daily meeting, often revisiting prior problems and concerns.

When an issue is identified that requires attention and discussion, you must discuss it as soon as possible. When many people are involved in determining the issue, it is often a problem affecting the work of large groups of people. It deserves to be resolved as soon as possible. Therefore, while a scrum of scrums meeting may last only fifteen minutes, everyone should budget more time to discuss potential problems.

Agenda of Scrum of Scrums

Agenda of Scrum of Scrums

An excellent scrum of scrums agenda should reflect the format of the daily Scrum, which has the following questions to answer:

  • What achievement has the team made since the last Scrum of Scrums meeting?
  • What will your team do before we meet again?
  • What limitations or hurdles are holding the team back?
  • Can an action taken by one team interfere with another team’s work?

The Scrum of Scrums meeting begins by answering these four questions by each participant present in a relatively short and fast-paced manner. This helps the scrum ambassador ensure the operational effectiveness of each team and that they are working towards the common goal of the project.

During this part of the meeting, the facilitator should encourage participants to raise questions and issues but not discuss possible solutions until everyone has had a chance to answer the above questions. 

One of the best techniques to achieve this is to leave the names out of the conversions, which can ultimately help you keep the discussion at the appropriate level of detail. This process aims to create a sense of coordination and cooperation between all the teams by involving cross-team synchronization across the organization.

Once the process is complete, the focus of the meeting shifts to address the issues and challenges discussed in the initial phase or maintained on the Scrum of Scrums backlog.

SoS in Large Organizations

A Scrum of Scrums framework can be very effective in large organizations with multiple teams, provided the Scrum of Scrum meetings are well-run and focus on solving issues that affect teams. 

The purpose of a Scrum of Scrums meeting is not to report the progress of development teams to manage but rather make sure that the individual teams are fulfilling their sprint goals and that the overall project goal is accomplished.

Did you find the video snippet on What are the benefits of smaller pizza-sized teams? to be insightful? We have a ~22 min video where Mitul Makadia gets into the weeds, and we discuss about Implementing & Scaling Agile to streamline Software Development. Take a look –

Conclusion

Scrum of Scrums is a unique approach to lead your organization towards agility. It’s a method of holding meetings and tracking progress while maintaining productivity. SoS ensures that meetings are more efficient, streamlined, and effective. It can help your organization become more agile—as it allows for faster development cycles and improved communication amongst the various teams involved in any given project.

We hope you enjoyed learning about Scrum of Scrums and how you can implement it to help your team deliver products in a timely and cohesive manner. 

Also read : A Comprehensive Guide to Scrum Sprint Planning.

With over 12 years of experience in addressing business challenges with digital transformation, we have what it takes to help companies bridge the gap between digital vision and reality.

A perfect software product demands an equally excellent execution methodology. At Maruti Techlabs, follow Agile, Lean, and DevOps best practices to create a superior prototype that brings your users’ ideas to fruition through collaboration and rapid execution. Our Agile experts can also help you identify the possible impediments that can be destructive for your business in achieving sprint goals.

Get in touch with us for a free consultation and learn how our product development services can transform your business vision into market-ready software solutions.

Mitul Makadia
About the author
Mitul Makadia

Mitul is the Founder and CEO of Maruti Techlabs. From developing business strategies for our clients to building teams and ensuring teamwork at every level, he runs the show quite effortlessly.

Posts from this authorred-arrow
card1
Agile - 17 MIN READ
The Ultimate Guide to Scaled Agile Frameworks: SAFe, LeSS, DA, Scrum@Scale
Check out the strategies & points to consider while choosing the right scaled agile framework.
blog-writer
Mitul Makadia
card1
Agile - 18 MIN READ
Understanding Scrum Board: Structure, Working, Benefits & More
Learn everything about the scrum board, its functionality, how they work & why you should choose them.
blog-writer
Mitul Makadia
card1
Agile - 12 MIN READ
A Comprehensive Guide To Scrum Sprint Planning
Explore the essential topics related to scrum sprinting and learn about how the process works.
blog-writer
Mitul Makadia