Scaling Agile @ Spotify – Quick Review Notes

Core unit; autonomous, cross-functional mini-startups (≈ $30$ + total across $3$ cities)
Own mission & product slice (e.g., Android client, Radio)
Choose workflow (Scrum, Kanban, mix)
Lean Startup mindset → “Think it, build it, ship it, tweak it”
Continuous learning: each member may spend $10\%$ time on hack days/weeks
Roles
- Product Owner – prioritises "what", maintains backlog & aligns with roadmap
- Agile Coach – facilitates retrospectives, planning, process improvement
Goal: zero blocking dependencies & direct stakeholder contact

Collection of related squads (< $100$ people ⇒ Dunbar limit)
Led by Tribe Lead – creates optimal habitat, co-locates squads, hosts regular demos
On-demand "scrum-of-scrums" for multi-squad initiatives

Functional peer group inside one tribe (e.g., web dev, testing)
Chapter Lead = line manager and active squad member; nurtures skills, salaries, growth

Voluntary, org-wide communities of interest (e.g., Web Tech Guild, Agile Coach Guild)
Cross-tribe, share knowledge, tools, practices; coordinated by Guild Coordinator

Regular surveys map blocking/slow dependencies; drive reprioritisation or architecture change
Dev–Ops partnership: Ops "builds the road", squads self-service releases

Service-oriented: > $100$ deployable systems (clients & back-end services)
System Owner (often a pair Dev + Ops) safeguards quality, scalability, debt; ≤ $10\%$ time
Chief Architect steers cross-system principles; squads retain final design authority

Quarterly squad health survey (PO, Coach, Influence, Release ease, Process, Mission, Org support)
Rising employee satisfaction (score $4.4/5$ as of $04/2012$ ) despite rapid growth from $30$ → $250$ tech staff in $3$ years