BROADCASTS.com

b'

This week, Dan Neumann is joined by his co-host, Sam Falco, principal trainer and professional scrum trainer at AgileThought.

\\xa0

Together, they\\u2019re exploring a question that was sent in by a listener. They asked Dan and Sam to share their take on \\u201cthe Spotify Model.\\u201d The popularized model was first introduced in 2012 by the whitepaper, \\u201cScaling Agile @ Spotify\\u201d and described a \\u201cpeople-driven, autonomous approach for scaling agile that emphasizes the importance of culture and network.\\u201d

\\xa0

Often, organizations will look at a successful company and say, \\u201cHow can we emulate what they do?\\u201d rather than, \\u201cHow can we emulate how they think?\\u201d There is a desire to mimic a pattern that another organization created because it fits their context, environment, people, and processes. However, installing the Spotify model can be fraught with danger because you\\u2019re not Spotify in 2012.

\\xa0

If you have your own question for the Agile Coaches\\u2019 Corner that you want Dan and Sam to answer in a future episode, you can send it in at AgileThought.com!

\\xa0

Key Takeaways

Why wouldn\\u2019t the Spotify Model work for your organization?

Just because you see somebody do something someplace else, doesn\\u2019t mean it\\u2019s going to work for you \\u2014 because you\\u2019re not them

You shouldn\\u2019t look at a successful company and say, \\u201cHow can we emulate what they do?\\u201d but rather, \\u201cHow can we emulate how they think?\\u201d (i.e. \\u201cthe Spotify Model\\u201d worked for Spotify, but will not work for your company \\u2014 emulating is not likely to bring you success)

The model may not be applicable \\u2014 and even if it is, there is going to be resistance and additional challenges will be exposed that will need to be addressed

Parallels between how organizations bring in the Spotify Model vs. how they bring in the Scrum framework:

With both, if you don\\u2019t do all of the elements, success is less likely

The Scrum framework, however, is a lot easier to adopt (preferably, adopt the Scrum framework and use it to find out what processes work for your organization)

Installing the Spotify Model can be fraught with danger because you\\u2019re not Spotify in 2012

You could try implementing some of the Spotify Model\\u2019s approaches (but most importantly, make sure it works for your organization)

When it comes to implementing any type of framework or model, the early questions should be: \\u201cWhat do you hope to accomplish? Why do you want to install this model or adopt this framework? What\\u2019s not working for you now and how do you think this will fix it?\\u201d This way, you can evaluate and measure\\xa0

Regardless of what model you\\u2019re proposing, think about: What does success look like? Why are you doing it? What is the problem you\\u2019re trying to solve?

Tips for adopting any model or framework:

Look at what\\u2019s working (and not working) within your own organization and have discussions on what to do next based on this

Adopt an experimental mindset

Be clear about the problem(s) you\\u2019re trying to solve as an organization

Be clear about how you\\u2019re measuring success

Look at all of the components of whatever you\\u2019re trying to adopt and ask, \\u201cHow will this work here?\\u201d, \\u201cWhat will prevent this from happening?\\u201d, and \\u201cWhat exists in our current system that is antithetical to these components?\\u201d

Approach the question of \\u201cShould we adopt _______ model or framework,\\u201d with empathy and humility \\u2014 whatever is being suggested (by whoever it may be) is trying to help the organization; not hurt it

How to ensure that implementation of a model or framework is successful:

Facilitate and make sure that you have all levels of the organization involved

Ask: \\u201cHow is it that we can maintain our current system and adopt a new system and still be successful?\\u201d

Remember: The current system is not going to change overnight

Note: Your journey will not be a straight shot from point A to point B

No matter the model or framework, the organization\\u2019s DNA is going to respond in unexpected ways \\u2014 be prepared for the unexpected

Bureaucracy kills innovation \\u2014 if you want to be innovative, you need to kill bureaucracy

It can be extremely beneficial to get an outside perspective and bring someone in outside of your organization

\\xa0

Mentioned in this Episode:

The Spotify Model

\\u201cScaling Agile @ Spotify,\\u201d by Henrik Kniberg & Anders Ivarsson

Humanocracy: Creating Organizations as Amazing as the People Inside Them, by Gary Hamel and Michele Zanini

Agile Coaches\\u2019 Corner Ep. 5: \\u201cExploring an Experimental Mindset with Adam Ulery\\u201d

Agile Coaches\\u2019 Corner Ep. 120: \\u201cBuild Better Teams with Sam Falco\\u201d

The Tuckman Model

Jira

LiberatingStructures.com

Wicked Questions | LiberatingStructures.com

Agile Coaches\\u2019 Corner Ep. 122: \\u201cThe Journey of an Agile Transformation with Quincy Jordan\\u201d

\\u201cRegardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.\\u201d \\u2014 Norman Kerth
Project Retrospectives: A Handbook for Team Review, by Norman L. Kerth

Buyology: Truth and Lies About Why We Buy, by Martin Lindstrom

\\xa0

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!