[NYC Scrum] The top 3 points you should have paid attention to in the Spotify Engineering Culture videos that aren’t Squads, Chapters, Tribes, Guilds.pdf
•
0 likes•16 views
The key points from the Spotify engineering culture model that are more important than their structural elements like Squads and Chapters are: 1. Aligned autonomy, which is achieved through a clearly expressed product strategy and empowered product teams. 2. Trust-at-scale, facilitated by cross-pollination between teams and a culture of mutual respect. 3. Decoupling technical services and product capabilities according to their volatility and differentiation. These allow experimentation without blocking other work.
Recommended
More Related Content
Similar to [NYC Scrum] The top 3 points you should have paid attention to in the Spotify Engineering Culture videos that aren’t Squads, Chapters, Tribes, Guilds.pdf
Similar to [NYC Scrum] The top 3 points you should have paid attention to in the Spotify Engineering Culture videos that aren’t Squads, Chapters, Tribes, Guilds.pdf (20)
More from Jason Yip
More from Jason Yip (20)
Recently uploaded
Recently uploaded (20)
[NYC Scrum] The top 3 points you should have paid attention to in the Spotify Engineering Culture videos that aren’t Squads, Chapters, Tribes, Guilds.pdf
- 1. The top 3 points you should have paid attention to in the Spotify Engineering Culture videos that aren’t Squads, Chapters, Tribes, Guilds Jason Yip for NYC Scrum The top 3 points you should have paid attention to in the Spotify Engineering Culture videos that aren’t Squads, Chapters, Tribes, Guilds | by Jason Yip | Medium
- 2. When most people say “Spotify Model”, they’re only thinking Squads, Chapters, Tribes, Guilds
- 3. When it comes to product development culture, structure is the last thing you should be worried about, not the first.
- 4. The 3 points that are more important than structure: 1. Aligned autonomy; 2. Trust-at-scale; 3. Decoupling …without even looking at your specific context
- 7. Alignment and autonomy are not two ends on a scale but two dimensions on a 2x2 matrix.
- 8. Clear problem but told exactly how to solve it “Shut up and follow orders” Aligned autonomy “Do whatever you feel like”
- 9. 2 parts to aligned autonomy 1. Clearly expressed product strategy 2. Empowered Product Teams (aka Squads)
- 10. Clearly expressed product strategy
- 11. The kernel of good product strategy 1. Diagnosis based on data and insight; 2. Guiding policy, that is, a set of beliefs describing the general approach to overcome the identified problems; 3. A key set of coherent actions, or more accurately bets.
- 12. Spotify Rhythm - how we get aligned - Crisp's Blog Diagnosis Guiding Policy Coherent action
- 13. From Gut to Plan: The Thoughtful Execution Framework | Spotify Design Diagnosis Coherent action Guiding Policy
- 14. 202x Vision TPDI strategy Guiding principles Top 5 priorities Diagnosis Guiding Policy Coherent action
- 15. Empowered Product Teams (aka Squads)
- 16. “Squad” is not a synonym for “team”; it’s a synonym for what Marty Cagan calls an “Empowered Product Team”. Empowered Product Teams - Silicon Valley Product Group : Silicon Valley Product Group (svpg.com)
- 19. Trust-at-scale
- 20. 2 contributors to trust-at-scale 1. Cross-pollination 2. Culture of mutual respect (aka People > *)
- 22. Cross-pollination humanises across boundaries Embedding Someone temporarily transfer to another team Liaisons Someone acts as the primary point-of-contact to another team. Effective liaisons are deliberately selected based on being well-respected and reliably good at developing relationships. Internal movement Someone permanently transfers to another team but still has relationships with their previous team
- 23. Squad interaction modes (Cara Lemon) ● Consult to not own ● Consult to own ● Temporary embed (outgoing) ● Temporary embed (incoming) ● Form temporary team ● Build to hand off ● Build to own Team interaction modes.| by Jason Yip | Medium
- 24. Culture of mutual respect (aka People > *)
- 25. Mutual respect encourages trust Role models Influential people consistently model respectful behaviour. Systems Systems incentivise respectful behaviour and dis-incentivise disrespectful behaviour. Stories Stories about what is good emphasise respect; stories about what is bad emphasise disrespect.
- 26. “Anything that is human is mentionable, and anything that is mentionable is manageable.” Fred Rogers
- 27. “No” to pretending politics and fear don’t exist; “Yes” to encouraging dialogue and safety in response to politics and fear.
- 28. Mutual respect means committing to shared meaning
- 29. This doesn’t get any back-and-forth.
- 30. This does (and shows respect).
- 31. Decoupling
- 32. Architecture should be coupled where product capabilities should be coupled and decoupled where product capabilities should be decoupled.
- 33. Exploit the Product Life Cycle (hbr.org) Experimentation Iteration Optimisation Outsourcing / shutdown
- 34. Technical services supporting product capabilities should not cause capabilities at different stages to be coupled.
- 35. Services supporting stable capabilities should not depend on services supporting more volatile capabilities.
- 36. Product capabilities Application Platform services Commodity Differentiating (better = $) Experimental Account management Audience management 3rd party measurement Payments Campaign management Customer-specific measurement? Advanced forecasting Decision optimisation Reporting Advanced pricing New client platforms New formats New targeting Ad serving console Order management Budget allocator Mobile client platform Audiences Google Ads integration Ad Studio Partner API Artists integration Native layer features Formats business logic
- 37. The 3 points that are more important than Squads, Chapters, Tribes, Guilds 1. Aligned autonomy; 2. Trust-at-scale; 3. Decoupling
- 38. Questions? And contact info jchyip@gmail.com https://www.linkedin.com/in/jasonyip/ https://jchyip.medium.com @jchyip@mastodon.online @jchyip (Threads, X)