Visited Spotify and said “Cool – I’ve been looking for someone who has implemented this matrix format since 1992 so it’s very welcome.” So how is this managed? Let’s take a look now. Spotify, like most agile software companies, started out using the Scrum framework. As the company culture evolved, Scrum was cast aside in favor of agile methods that were no longer tied to a framework, giving teams more autonomy. Each team (called a squad) is autonomous in defining how it works, and all squads have a mission, a product strategy, and their own OKRs, all of which are, of course, aligned with the rest of the company.
Spotify Squads How to scale Agile: The role of the squad. The basic unit of development at Spotify is the Squad. A Squad is similar to a Scrum team and is designed to look like a small startup. They sit together and have all the skills and tools they need to design, develop, test, and New Zealand Telemarketing Data release to production. Squads are self-organizing teams that decide how they work—some use Scrum, some use Kanban, and some use a combination of these methods. Each group has a long-term mission, such as building and improving the Android client, creating a Spotify radio experience, expanding the backend systems, or providing a payment solution.
The following diagram illustrates how different teams are responsible for different parts of the user experience. This is an old version of the Spotify product, but you can get an idea of how each squad is responsible for different parts of the product. Teams are encouraged to apply Lean Startup principles such as MVP (minimum viable product) and validated learning. MVP means releasing early and often, while validated learning means using metrics and A/B testing to find out what really works and what doesn’t.