Agile at Scale Advanced


A Tribe gathering a group of Agile Squads (also called Feature Teams) aligned on Value Chains. The vision and the value prioritizes are provided by the Product Management Team (PMT). Chapters enforce consistency cross Agile Squads for a given skill. They also support knowledge growth and sharing.


In this category of posts, discover the advanced principles of Agile at Scale described in this blog as a combination of Spotify and SAFe, sometimes called Spotisafe. Those principles cover League, Agile Squad Design, Horizontal Management and the change in roles and responsibilities.


What is a League in Agile at Scale? What is the difference with a Guild?

The Agile at Scale League is not coming from Spotify neither from SAFe. We will review the definition and the characteristics of a League in Agile at Scale. Then we will point out the differences with a Chapter or a Guild. At last, we will check the role of the League Manager and the League Members.


How to design Agile Squads? How to align them on the Value Chains?

We will explore the principles of alignment on Value Chains. Firstly, we will see how to limit the need for scaling agile when possible. Then we will review how to align the Tribes and the Agile Squads on the Value Chains. At last, we will learn about the setup of an Agile Train for cross organization initiatives.


What is the Spotify Management? Why going for horizontal management?

We will learn about vertical and horizontal managements. Then we will check the reasons for going to horizontal management. To continue, we will explore the prerequisites of horizontal management and team empowerment. At last, we will discover what is the journey to Agile Squad’s autonomy.


What are the roles and responsibilities impacted in Agile at Scale?

We will explore the roles and related responsibilities impacted in Agile at Scale. Then we will see how these responsibilities are reallocated.

Scroll to Top