Agile Spotify style

Spotify is well known for its music. We can also learn a lot about their internal dealings. In this post I collect everything that clarified my understanding of Agile Spotify Style. How do they x, y and z, Spotify’s business model, customers and the like. I aim to understand more of the culture, process and context in which Agile Spotify style is successful. This Post is and will, by the nature of agile, be work in progress (WIP). Contributions are very welcome.

Engineering Culture
To start you off a nice video to explain their Engineering Culture;(Video 13min, Henrik Kniberg)

Culture over Process presentation (pdf 95pages, Henrik Kniberg)

Culture eats process for breakfast

Building products Spotify style
Spotify thought hard about reducing product development risk and came up with a 4 stage model;

  1. Think It
  2. Build It
  3. Ship It
  4. Tweak It

You find a complete description in this 10 page pdf by Henrik Kniberg; How Spotify builds products

Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds (pdf 14 page’s, Henrik Kniberg)

  • Squad : The basic unit of development at Spotify.
  • Tribe : A tribe is a collection of squads that work in related areas
  • Chapter : Small family of people having similar skills and working within the same general competency area, within the same tribe
  • Guild : A Guild is a more organic and wide-reaching “community of interest”, a group of people that want to share knowledge, tools, code, and practices

Scrum checklist (English version 2.2 pdf 2 pages, Henrik Kniberg)
Scrum checklist (dutch, pdf 2pages, Henrik Kniberg)

Latest Spotify News
To understand the context and challenges that Agile Spotify Style is taking on, a couple of links to the latest news:

Henrik Kniberg
More from Henrik (below on his page is a list with links to more material)