Tribes @ Spotify
Tribes @ Spotify
The Big Picture
The horizontal dimension is for sharing knowledge, tools, and code.
the vertical dimension in the matrix: people are grouped into stable co-located squads, where people with different skill sets collaborate and selforganize to deliver a great product
kind of a feature team
sit together and have all the skills and tools needed to design, develop, test, and release to production
self-organizing team that decide their own way of working
one long term mission
each squad sticks with one mission and one part of the product for a long time to become experts in that area
hack days / weeks
to promote learning and innovation, each squad is encouraged to spend roughly 10% of their time on “hack days”
one product owner
The product owner is responsible for prioritizing the work to be done by the team, but is not involved with how they do their work
doesn’t have a formally appointed squad leader
supported by agile coaches
a squad also has access to an agile coach, who helps them evolve and improve their way of working
“incubator” for the squad
collection of squads
A tribe is a collection of squads that work in related areas
have a fair degree of freedom and autonomy
one Tribe lead
regular tribe gatherings
Tribes hold gatherings on a regular basis, an informal gettogether
within a tribe
Chapters are always local to a Tribe
"group with similar skills"
The chapter is your small family of people having similar skills and working within the same general competency area, within the same tribe.
one chapter lead
"community of interest"
A Guild is a more organic and wide-reaching “community of interest”, a group of people that want to share knowledge, tools, code, and practices.
one guild coordinator
focus on the integrity of the system as a whole
coordinator and guides people who code in that system to ensure that they don’t stumble over each other
focuses on things like quality, documentation, technical debt, stability, scalability, and release process.
provides an architectural vision
coordinates work on high-level architectural issues that cut across multiple systems
Lean Startup principles & tools
MVP (minimum viable product)
releasing early and often
using metrics and A/B testing to find out what really works and what doesn’t
says that most people cannot maintain a social relationship with more than 100 people or so
simple graph for dependencies
to track how the various types of dependencies increase or decrease over time
PO is the “entrepreneur” or “product champion”, focusing on delivering a great product, while the chapter lead is the “professor” or “competency leader”, focusing on technical excellence.
healthy tension between these roles, as the entrepreneur tends to want to speed up and cut corners, while the professor tends to want to slow down and build things properly
Copy the code to embed this map into your article. The embeded map can even be zoomed in / out
COPY TO CLIPBOARD
Open in XMind Gallery.
Exit full screen.