Agile Transformations Using The “Spotify Model”
summary
Case study of a two year transformation at Telenor uses tribes and squads and changes in sourcing to insource engineering to recreate empowered product teams. Metrics move: cycle time for a new feature falls from 170 to 27 days and overhead drops from 41 to 32 while IT engagement rises from 22% to 58% in two years. Practices include chapters, weekly product owner team lead agile coach trios and recurring big room planning to align autonomy and outcomes.
AI-written summary · about
chapters (12)
- 0:00Intro
- 6:04Lessons are based on
- 6:482 types of lessons learned
- 9:31Understand where you are
- 12:36Develop vision & principles
- 16:20It's a marathon, not a sprint
- 24:38Integrate business & IT through mission based tribes
- 28:27The autonomous squad
- 32:56Prepare to insource
- 40:09Aligned autonomy
- 44:48So how did it go?
- 46:43Outro
related talks
46mScaling Agile in your Organization with the Spotify Model
41m3 Ways Your Operating Model Can Cultivate An Agile Mindset
48mAgile at scale at Spotify
51mSabotaging a Transformation
45mAgile Transformation Or Just Another Restructure?
36mOne Agile Transformation and two beers please
44mTransformation Tales
50mAgile Outside IT Companies & Departments: Real Stories of Transformations