Challenges and Promises of the Spotify model

This presentation has been given at the conference "La journée Agile" in June 14th 2019 at Liège (Belgium).

We talked about why you should adopt the Spotify Model to scale your organisation but also the challenges that may slow down or avoid its adoption.

Transcript

1. Challenges and Promises of the Spotify model Journée Agile 2019 - Lîdje (Liège) Said Eloudrhiri - Noratek @eloudsa
2. •In IT since 1992 •Agile coach, Developer •Trainer, Speaker •Founder of Noratek •Co-founder of ChainSkills @eloudsa https://www.linkedin.com/in/eloudsa
3. Disclaimer • I’m not related to Spotify or any related subsidiaries. • The views expressed in the presentation are my own. • The material (images, videos, concepts, etc.) used in this presentation remains the property of their owners.
4. Why talking about the Spotify Model?
5. The Kool company • Business departments • IT Department • Products and Services • Home-made solutions • Worldwide customers • Agile
6. IT
7. ARCHITECTURE PMO WEB APPS MOBILE APPS CRM FINANCE SERVICES ACCOUNT SERVICES CARE SERVICES IT OPERATIONS (HELP DESK, INFRASTRUCTURE, SECURITY)
8. Project mindset
9. WEB ACCOUNT FINANCE IT OPERATIONS Project 1 BUSINESS
10. WEB ACCOUNT FINANCE IT OPERATIONS Project 1 BUSINESS Project 2 BUSINESS IT OPERATIONS ACCOUNT MOBILE WEB CARE
11. WEB ACCOUNT FINANCE IT OPERATIONS Project 1 BUSINESS IT OPERATIONS Project 3 BUSINESS WEB Project 2 BUSINESS IT OPERATIONS ACCOUNT MOBILE WEB CARE
12. WEB ACCOUNT FINANCE IT OPERATIONS Project 1 BUSINESS IT OPERATIONS Project 3 BUSINESS WEB Project 2 BUSINESS IT OPERATIONS ACCOUNT MOBILE WEB CARE ACTIVATION BILLING Project 4 BUSINESS IT OPERATIONS FINANCE ACCOUNT CARE
13. WEB ACCOUNT FINANCE IT OPERATIONS Project 1 BUSINESS IT OPERATIONS Project 3 BUSINESS WEB Project 2 BUSINESS IT OPERATIONS ACCOUNT MOBILE WEB CARE ACTIVATION BILLING Project 4 BUSINESS IT OPERATIONS FINANCE ACCOUNT CARE PMO + ARCHITECTURE
14. Project 2 BUSINESS IT OPERATIONS ACCOUNT MOBILE WEB CARE
15. €
16. €€€€€
23. IT
24. BUILD THINK RUN
25. ACTION BUILD THINK RUN
26. • They think it • We build it • They run it Business Think Developers Build IT OPS Run P R O J E C
 T
31. Chief Dir CEO Chief Deputy Dir Dir Dir Dir
33. Chain of command
34. S C A L A B I L I T Y
35. SCALABILITY
38. IT
39. NEW IT
40. Product mindset
41. Customer
42. Customer Product
43. Product Team Customer
44. Product Team Customer
45. SCALABILITY
46. S C A L A B I L I T Y
47. ACTION BUILD THINK RUN
48. BUILD THINK RUN A C T I O N
49. Being Product Minded to be more Customer Centric
50. Target • We think It • We build It • We run It PRODUCT Product Team Think Build Run
51. Business Think Developers Build IT OPS Run P R O J E C
 T PRODUCT Product Team Think Build Run ???
54. Spotify Model Promises
55. ARCHITECTURE PMO WEB APPS MOBILE APPS CRM FINANCE SERVICES ACCOUNT SERVICES CARE SERVICES IT OPERATIONS (HELP DESK, INFRASTRUCTURE, SECURITY)
56. Agile coach QA Front Dev OPS Back Dev BA SQUAD Architect
57. Agile coach QA Front Dev OPS Back Dev BA SQUAD Architect
58. QA Front Dev OPS Back Dev PO SQUAD Architect Agile coach BA
59. SQUAD PO • Mini startup • Agile • Feature-based • MVP • Reduce time-to-market • Autonomy • Continuous improvement
60. PO PO PO PO
62. PO PO PO PO
63. PO PO PO PO
64. PO PO PO
65. Responsibility SQUAD
66. SQUADS
67. Tribes
69. Tribe Lead Tribe Architect TRIBE Tribe Lead Tribe Architect TRIBE Tribe Lead Tribe Architect TRIBE
70. SQUADS
71. TRIBE TRIBE TRIBE TRIBE
72. SQUADS BUSINESS
73. TRIBE TRIBE TRIBE TRIBE BUSINESS
74. SQUADS CUSTOMER JOURNEY
75. TRIBE TRIBE TRIBE TRIBE CUSTOMER JOURNEY
76. Silos
77. Chapters API Chapter
78. Chapters UX/UI Chapter
79. Silos
80. Guilds GDPR Guild
81. Guilds Agile Guild
82. Guild Chapter Squad Tribe
83. ACTION BUILD THINK RUN
84. Autonomy Think the product? BUSINESS
85. Digital Guild Silos
86. Digital Guild
87. ACTION BUILD THINK RUN
88. BUILD THINK RUN A C T I O N
89. Autonomy SQUAD Website SQUAD OPS INFRA Release the product?
90. Guilds DEVOPS Guild
91. Autonomy SQUAD Website SQUAD OPS INFRA
92. Autonomy SQUAD Website SQUAD OPS Enablers INFRA
93. BUILD THINK RUN A C T I O N
94. BUILD THINK RUN A C T I O N
95. Time, Time, Time • Chapters • Guilds • More DevOps • Focus on products • Agile ceremonials • One team spirit with Business • Learn and share
96. Project Run Other
97. My Time Project Run My Time Other 10 %
98. 1. Proactive: improve the quality and the stability of our products 2. Craftmanship: Use the best tools, the best practices and be more autonomous to become more DevOps 3. Collaboration: improve what we do by sharing what we know within Chapters and Guilds 4. Ideation: gives a new breath to the company by bringing your ideas My Time
99. Guild Chapter Squad Tribe My Time
103. Is it so easy?
104. Is it so easy?
105. Spotify Model Challenges
106. #1: The name
107. Problem: You are not Spotify!
108. Solution: Use your own name
109. #2: Dogmatism
110. Problem: Driven by the book
111. Solution: Learn, Experiment and Adjust
112. #3: The organisation
113. Problem: Transform all services
114. Solution: Leverage IT Business
115. Solution: Leverage IT Business
116. Solution: Leverage IT Business
117. #4: Trust vs Control
118. Problem: Control
119. Solution: Trust
120. #5: Autonomy & DevOps
121. Problem: Bottleneck
122. Solution: More DevOps
123. #6: My (Waste of) Time
124. Problem: Don’t want to change
125. Solution: Show by the example
126. #7: (Dis)Engagement
127. Problem: Collaborators disengagement
128. Problem: Collaborators disengagement
129. Solution: Engaged collaborators
130. Solution: Engaged collaborators
131. Solution: Engaged collaborators
132. Solution: Engaged collaborators
133. Solution: Engaged collaborators
134. #8: (Fr)agile
135. Problem: not agile or not really agile
136. Solution: Be agile first
137. Solution: Be agile first Ad hoc Agile Team agility Scale agile Agile mindset
138. #9: Roles
139. Problem: I don’t know who I am Existing Roles New Roles ?
140. Solution: Make it simple Existing Roles New Roles
141. #10: Be helped
142. Problem: Implement it without experience
143. Solution: Be helped
144. • Rename it to adopt it • No dogma but stick to to your reality • Start locally • Trust over control • More DevOps culture • Let people to think with “My Time” • Make your engaged collaborators, your ambassadors • Be agile first • Explain existing/new roles and responsibilities • Learn and be helped from people having prior experience In summary
145. Questions?