Devs fight your Battle! A Pledge for cross-functional Teams
summary
Company reorganizes into fully cross-functional, self-governing squads inspired by Spotify and executes a one-day 50 people Big Bang move; a two-day embedded developer+service experiment cuts a 0.6% reclamation rate by almost 50% reduction in reclamation. Teams own customer segments, merge marketing and dev skills, and publish progress on Workplace; an intended infrastructure squad collapses and infrastructure squad dissolved as teams absorb work. Pain points: legacy tech and short-term feature focus, occasional 15-person squads, and ongoing experiments to balance platform work, quality and speed.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 13:28Need for change
- 27:51First cross-functional teams
- 33:45Self-governing teams
- 41:14Challenges after restructuring
- 50:42Product platform teams
- 56:08Q&A
related talks
46mScaling Agile in your Organization with the Spotify Model
26mThe Rise and Fall of Feature Teams
16mEmpowering Teams To Change
47mDeath Of The "Spotify Model"
46mBeyond agile Behind the scenes of the Tech giant unicorns
22mThe Rise and Fall of Feature Teams
58mReturn of the rockstars? Building great teams in challenging times
43mThe #Spotify model - Does copy/past implementation work?