Spotify's model dates back to 2011 when Henrik Kniberg&amp; Anders Ivarsson published a Whitepaper: Scaling Agile @ Spotify with Tribes, Squads, Chapters, and Guilds. It was not intended to be published as a framework but as a generic overview of how product development is organised at Spotify, including team hierarchy, how teams are organised and what type of company culture will make it work.

The Spotify Model

Squads are organised into the relevant tribes. Tribes consist of less than 100 people.A tribe lead is assigned to each tribe and ensures everyone has what they need to thrive. Crossover between squads is inevitable, which creates certain dependencies, which slow teams down. The model aims to lessen dependencies and prevent bottlenecks.

Tribes

Autonomous work is the future of successful agile product development.&nbsp; The main benefit of the Spotify model: Teams are empowered to make their own decisions and work in the way that best suits them. It encourages transparency, trust, collaboration, and experimentation, and lead to better products.&nbsp;

Autonomy

Guilds are more general areas of interest - for example, testing.&nbsp; Everyone directly involved in testing will join the guild, but even those who are simply interested in it may also join in order to learn.&nbsp;

Guilds

When teams take charge of themselves and make their own decisions, they’re can work faster and avoid bottlenecks.&nbsp; The model encourages informal gathering and information sharing, without too much ceremony or formal process.&nbsp;

Fewer bottlenecks and red tape

Spotify has 100 distinct systems which form the overall product. When squads update one, they may need to update several to implement the changes they’ve been working on.&nbsp; The risk: The architecture can go awry if everyone is only focusing on a small chunk of it at a time.&nbsp; Solution: A system owner who owns the integrity of the architecture can mitigate this risk.&nbsp;

Risk to system architecture

The Spotify model doesn't have to be used as a whole. For example, implementing some of the agile principles may also work. Rearranging the structure of your company is a significant risk and a considerable investment. Because the Spotify model is working for them, it doesn't mean it was designed to work for everyone. It may not be a good fit for you.&nbsp;

It won’t work for every company

<ul><li>A squad is the most basic unit of development.&nbsp;</li><li>Each squad is designed to function as its own mini-startup, with all of the skills needed to build a product, (design, testing, engineering, etc).</li><li>Teams are self-organizing, and each squad can choose the framework that works best for them, such as Scrum, Kanban, etc.</li><li>Each squad has their own long-term goal, and own a particular part of the product.</li><li>Squads are encouraged to employ lean product principles like A/B testing and releasing MVPs.</li></ul>

Squads

Members of different squads with similar skills or who work on similar problems form cross-squad chapters that meet regularly to keep up to date on what others are working on.&nbsp; The frequent knowledge sharing ensures that there is helpful communication between the squads.

Chapters

When building digital products, we all want to feel like we’re doing it the right way. And nothing feels more satisfying than feeling like you’ve finally found the perfect framework or methodology…

Fewer bottlenecks and red tape

Similar ideas to Fewer bottlenecks and red tape

Applying the Heart/Will/Head model to yourself