Hacker News new | ask | show | jobs
by chrisoverzero 1792 days ago
The Spotify model is about how people are arranged. It has nothing to do with development methodology or work tracking. From the whitepaper introducing the Spotify model (https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScal...):

> [Squads] are a self-organizing team and decide their own way of working – some use Scrum sprints, some use Kanban, some use a mix of these approaches.

2 comments

And here's a version that's 8 years more recent [1]

> The foundation of the model is the squad and it acts like a Scrum team.

The Spotify model resembles Scrum@Scale which is why I mentioned it. Scrum is a development methodology.

1. https://www.pmtoday.co.uk/spotify-scaling-agile-model/

From your article:

> Each of the squad has complete freedom to choose their agile methodology. So some squad uses Scrum sprints, some use Kanban and some uses mix of scrum and kanban. Sometimes to release early, squads apply the Most viable product (MVP) technique too.

The Spotify model is not related to Scrum. It organizes people. How those people manage their work is not related to how the people are organized. An article explaining the Spotify model in terms of Scrum isn’t a counterexample to that.

> some use Scrum sprints, some use Kanban, some use a mix of these approaches.

Is there only one "The Official" ScrumBan, or can anyone make their own?