Agile at scale at Spotify
summary
Spotify describes concrete practices for keeping velocity while scaling: autonomous squads (5–7 engineers) that deploy independently, grouped into ~70 tribes with chapters and guilds for shared craft, backed by a loose service‑based architecture and continuous delivery pipelines. Metrics cited: ~24 million active users, 6 million subscribers, 20,000 songs added daily. Processes include bootcamps to ship in week one, quarterly OKRs, company postmortems after major outages, and deliberate experiments that sometimes fail and sometimes produce reusable platforms.
AI-written summary · about
chapters (15)
- 0:00Start
- 4:02Autonomy
- 5:32Example squads
- 8:24Process that fits
- 12:44A new squad is born ...
- 14:52Structure and alignment
- 15:48Chapters
- 16:59Chapter Lead
- 18:07Personal development
- 24:18Network organization
- 25:17Dependencies
- 37:02Projects
- 39:13Road Manager
- 41:40Improvement
- 44:022x speed challenge
related talks
46mScaling Agile in your Organization with the Spotify Model
39mOwn your speed
43mThe #Spotify model - Does copy/past implementation work?
29mThe Spotify model - Does copy paste implementation work
49mMicroservices at Spotify
52mHow do we do product at Spotify
46mBeyond agile Behind the scenes of the Tech giant unicorns
47mAgile Transformations Using The “Spotify Model”