Scrum of Scrums: Its Agenda and Purpose (2024)

What is a Scrum of Scrums?

We all know that a scrum is an integral part of agile methodology, a daily face to face meeting lasting about 15 minutes or so. The agile team, usually composed of between five to ten people, hunkers down and hashes out where the team stands in terms of work progress, what they’re working on now, how long it will take, and what potential obstacles exist.

A scrum of scrums involves multiple scrum teams meeting together by having one or two representatives from each separate scrum getting together. Hence, a scrum of scrums. Unlike regular scrum meetings, however, scrum of scrum gatherings don’t have to meet daily; twice a week is enough in most circ*mstances.

Are you a professional who is aspiring to be a Certified ScrumMaster? Then check out the CSM certification course now.

Why We Need a Scrum of Scrums?

Since scrum teams work best with under ten members, larger companies create more groups to accommodate the higher number of developers. However, multiple scrum teams must somehow stay in contact and coordinate their efforts to avoid pitfalls such as redundancy and inefficiency.

That’s why the best solution is a scrum of scrum meeting, which brings together representatives chosen from each agile team. This way, no team gets left out of the loop, and everyone’s resources get allocated in an efficient, productive manner.

Regarding scrum of scrum team size, conventional wisdom recommends following the same standards applied in the smaller-scale scrum meetings: no more than ten attendees. This limitation could force an organization to hold multiple scrum of scrums, which in turn can require a scrum of scrum of scrums, but we’ll save that one for a little later!

Benefits of a Scrum of Scrum

So what are these meetings useful for? Although we’ve briefly touched upon a few advantages, it’s worth listing them for easy reference.

• Easier for huge companies to use scrum methodology
• Streamlines collaboration
• Guarantees that every team stays informed since everyone is represented
• It provides a forum for airing out issues and difficulties, making problem-solving easier
• Facilitates consensus
• Provides a means of dealing with new, unexpected developments that potentially affect multiple groups or departments
• Reinforces each team’s role and keeps them on course, preventing them from drifting into another team’s lane

What are the Goals of a Scrum of Scrum?

They are pretty straightforward, and in line with what we’ve already discussed:

• The coordinate output from all the teams involved
• Integrate multiple team’s productions into a single entity
• Eliminate any bottlenecks

To that end, each team representative must answer each of these questions:

• What has your team accomplished since the last meeting?
• What problems arose, if any, that created a roadblock?
• What tasks does your team plan to accomplish before the next meeting?
• What output from your team’s future sprints do you anticipate interfering with the work of other teams, if any?
• Have you experienced any obstacles stemming from other teams?

These questions help each scrum “ambassador” contribute towards the ultimate success of the scrum of scrums. The key is to foster a sense of coordination and cooperation, also called cross-team synchronization, between all the teams.

Who is Involved in a Scrum of Scrum?

Speaking of teams, it’s time to discuss scrum of scrum team size and precisely who is involved in them. They should feature between five and ten participants, and conventional wisdom dictates that the representatives should be the Scrum Masters of each scrum team.

However, if each team sends only their Scrum Master, there is the risk of bringing a limited perspective to the scrum of scrums. For instance, it’s rare for a tech person to be the Scrum Master, and it’s exactly that kind of input that larger meetings may require. The possible need for technical input speaks to the idea of having two representatives from each team, maybe the Scrum Master and the tech person, or perhaps a member of the development team.

Optionally, the scrum of scrums should also include the product owner. This person’s perspective can potentially come in handy. Smart planners will invite product owners only if there is little to no risk that the meeting will lose its focus. The meeting shouldn’t be a forum for product owners to air grievances and attempt to make development decisions outside of their wheelhouse.

Then we have the issue of who runs the scrum of scrums, or to stay in the jargon, the scrum of Scrum Master. While many meetings function perfectly well as a self-leading body, a larger group meeting may require someone to step into the Scrum Master role.

The bottom line, any team or group that is responsible for a deliverable as part of the release plan should have a representative attending the scrum of scrums.

How to Conduct a Productive Scrum of Scrums?

Here are some tips for having an effective meeting:

• Make sure each team knows what points to share in the meeting. We covered those items above.
• Make sure to appoint the right people to the meeting. Same as the first item, each team needs to send the right person, and it’s not always the Scrum Master.
• Set the meeting length and frequency ahead of time. No more than twice a week, with a period between 30 minutes to an hour, tops. If you can keep it to the size of a regular scrum, 15 minutes long, then so much the better.
• Set aside time to solve problems. This isn’t just an exercise to get a status report.
• Create an environment where everyone feels at ease with sharing concerns and other information. That means creating trust and transparency with all the team members.
• Emphasize to each attendee that the information covered in the meeting must be brought back to each team and relayed clearly to them. If people aren’t informed, then why have these meetings in the first place?
• Remember that it’s a scrum of scrum meetings, not a status meeting. People aren’t here to only report on what they’ve done. Scrum meetings are more than this. Status meetings are holdovers from the waterfall methodology and have no place in this agile method.

What is a Scrum of Scrum of Scrums?

Yes, this is a thing. A scrum of scrum of scrums meeting brings the Scrum Masters of each scrum of scrum meeting together into an all-encompassing, large meeting. When the overall developer team size is so large that even breaking it down into scrum of scrum teams isn’t enough, it’s time to bring out the scrum of scrum of scrums.

Meetings of this magnitude are crucial in these cases because the more extensive the project staff, the higher the risk of things getting unwieldy, including communications breakdowns and confusion over individual team roles.

These meetings are often referred to as a large-scale Scrum (LeSS) and are designed to handle hundreds of developers.

Learning More About Agile and Scrum

Simplilearn has a comprehensive collection of resources regarding agile and scrum. You can learn how to control risk in agile project management, or learn about scrum project management. There are introductoryand advancedvideo tutorials as well.

If you’re planning on applying for a position as a Scrum Master, then you will want to prepare for that interview by checking out the Agile Scrum Master Interview Questions and Answers. And speaking of becoming a Scrum Master.

Have You Ever Considered a Career as a Scrum Master?

Simplilearn’s Certified ScrumMaster (CSM) Certification Training