Spotify engineering culture (part 1)

Here’s part 1 of short animated video describing our engineering culture (here’s part 2).

This is a journey in progress, not a journey completed, and there’s a lot of variation from squad to squad. So the stuff in the video isn’t all true for all squads all the time, but it appears to be mostly true for most squads most of the time :o)

Here’s the whole drawing:


(Tools used: Art Rage, Wacom Intuos 5 drawing tablet, and ScreenFlow)

Here’s Part 2.



  1. […] InfoQ: アジャイルにはたくさんのハンマーがあって、その多くは商業的な利益を動機としていますが、Spotifyの“モデル”はそういった商業目的のないモデルのひとつのように思われます。“モデル”を適用することについて、どのような意見をお持ちですか? […]

  2. […] A big change to the organization will be departmental structure and separation of powers. Under the agile mindset, small teams are established that possess the cross-functional skills to self-organize and solve problems proactively. A practical example of this would be seating charts changing so teams can sit together, as opposed to being separated by department. If a team can be thought of as vertically-integrated silos, then departments and homogenous skillsets can be thought of horizontal groupings. In many technology companies like Google and Spotify, these have been called “tribes”. […]