About the Book
There is an ongoing discussion in the Agile community about the Spotify model and the rationale for copying it. The discussion goes as far as saying: “There is no Spotify model, there is only the snapshot Spotify culture”. This statement seems to have become the fragile consensus and the equilibrium state for many Agilists. In parallel, there also exists physical evidence that the entity called the “Spotify model” exists. The evidence has a form of a significant number of companies which chose the “Spotify model” as a blueprint for their Agile transformations.
Why is this topic such an ignition point? Is this a good framing in the first place? Do we focus on the right questions? Personally, I learnt to stick with comparing things rather than trying to assess them in absolute terms, in isolation. So I reframe the subject and ask different questions: What value does introducing the Spotify model to organizations have? What are the alternatives? And how does the “Spotify model” compare to alternatives?
About the Author
When I worked in technology companies as a software engineer it hit me that solving tech problems was never a problem for tech geeks. The WHAT and WHY questions were. A company identity, mission and vision were. And on top of those - HOW we work together here was. And the leadership style was.
So I switched...
Check out my full profile at https://www.linkedin.com/in/piotrtrojanowski/