The #Spotify model - Does copy/past implementation work?
summary
Describes the concrete Spotify practices and what actually worked or failed: squads <10 developers as feature teams, tribes 100–150 people and alliances up to 300+, chapters that meet weekly with a chapter lead splitting time half coding half line management, release automation using feature toggles and release trains, limited blast radius and A/B testing, and quarterly two‑day planning with a confidence vote 1–5. Advises not to copy/paste but to tailor these elements to context.
AI-written summary · about
chapters (18)
- 0:00Spotify approach intro
- 3:58Model structure overview
- 7:14Squads and collaboration
- 10:28Tribes and dependencies
- 11:34Chapters and guilds
- 13:23Scaling the model
- 14:06Engineering culture practices
- 17:40Quarterly planning
- 25:24Showcase vs Sprint review
- 26:06Culture not framework
- 28:56Adoption principles
- 32:32Copy the model?
- 33:16Q&A knowledge sharing
- 36:06Team health checks
- 38:16Success stories
- 39:06Model in large corps
- 40:13Chief Architect role
- 41:40Q&A wrap-up
related talks
29mThe Spotify model - Does copy paste implementation work
01h 04mYou are not Spotify, and you don’t want to be
27mIs Spotify a good example?
48mAgile at scale at Spotify
46mScaling Agile in your Organization with the Spotify Model
39mOwn your speed
52mHow do we do product at Spotify
50mSpotify, from the Inside