Death Of The "Spotify Model"
summary
ING replaces the Spotify-style squads with micro teams of 3–4 developers, shifts left and standardizes on Azure DevOps + OpenShift + immutable containers (Docker/Kubernetes), plus platform services like Kafka and Cassandra. Results: 62% faster deployments and >50% more releases, four cloud engineers supporting 100+ devs, and measurable gains in throughput (dozens more backlog items per year). Problems surface in observability and SRE, so platform teams absorb monitoring and incident responsibility and a 2.0 SRE model is adopted to make the gains sustainable.
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:37Setting the scene
- 3:44What books inspired us
- 5:54Way of working at ING over time
- 6:59The "Spotify Model"
- 12:07Improving the journey
- 16:15Death of the IT manager
- 18:14MicroTeams
- 25:32Product thinking
- 28:30What happened to OPS?
- 31:07From Linux specialist to cloud engineer
- 36:29Is it all awesome?
- 40:05Rolling out at scale
- 45:24Conclusions
- 46:35Outro
related talks
46mScaling Agile in your Organization with the Spotify Model
29mThe Spotify model - Does copy paste implementation work
48mAgile at scale at Spotify
11mBreaking the (developer) silos
58mDevs fight your Battle! A Pledge for cross-functional Teams
43mThe #Spotify model - Does copy/past implementation work?
49mMicroservices at Spotify
46mBeyond DevOps: How and Why Companies Converge on Platform Models