It includes the team hierarchy, how teams are organized, and the kind of company culture needed to make the whole thing work.Īs an agile company, Spotify’s model champions the needs for collaboration, transparency, and simplicity, which makes it very attractive for other agile companies looking to make the methodology work for them. It was never intended to be published as a framework, but rather as a generic overview of how product development is organized at Spotify. “It’s just an example of how one company works.” Kniberg is often credited as being the ‘inventor’ of the model, but he’s the first person to tell you that’s not the case! And he’s also keen to impart that it was never meant to be something that people copied, or implemented at their own companies. The Spotify model dates back to 2011 when Henrik Kniberg & Anders Ivarsson, at the behest of their colleagues, published a whitepaper: Scaling Agile Spotify with Tribes, Squads, Chapters, and Guilds. Here, we’ll be going over what the Spotify model is, why it grew as a popular framework in Silicon Valley…and why Spotify doesn’t use it! (Yes, there’s a lot that Silicon Valley gets wrong about The Spotify Model!) Even if you’re not building a music streaming platform, the model presents a new way of empowering self-organizing teams and building a product loved by millions of users. And you might even have heard of their innovative framework for organising teams and scaling products in agile. You might have heard of the billion dollar company, Spotify. Unfortunately there are so many to choose from! So it’s important to do your research and figure out which ones are worth trying. And nothing feels more satisfying than feeling like you’ve finally found the perfect framework or methodology that’ll help you do that. When building digital products, we all want to feel like we’re doing it the right way. What Silicon Valley Gets Wrong About the Spotify Model.Challenge: It won’t work for every company.Benefit: Fewer bottlenecks and red tape.
0 kommentar(er)
