Member-only story
Agile at scale (Scrum of Scrum, Spotify, SAFe)
The Scrum rules are applied mostly only for one team. There are a few rules for team interoperation and external communication, but it’s not enough. There are several methodology, see Agile at scale. I just noticed a few which I had experience with.
This article is a part of my Scrum series, see with free links (including to this article):
I like Scrum. The good Scrum.

Scrum of Scrum (SoS)
It’s the most simple and well known method to schedule and integrate Scrum teams. Fortunately, I didn’t have to join SoS, I just heard some negative feedback from participants, mostly from tech people, who had Scrum Master roles. It was dull and exhausting for them.This meeting can easily become a progress meeting, where the process improvements and analysis were eliminated.
To allocate enough time for process improvements and analysis, a Product Owner (PO) sync can be introduced, which can focus on the progress. It’s only a possibility, the SoS efficiency depends on the control and authority of Scrum Masters.
Spotify model
This methodology was born in about 2014, at Spotify, see Henrik Kniberg about Spotify model.