Currently we at youngculture have mostly independed scrum teams. However, I always was wondering how huge companies like Microsoft, Apple, etc  handle hundreds and thousands of people with Scrum. Read below, Spotify made there way of implementation public. images-2

In the "traditional" scaling of scrum, as Craig Larman, Bas Vodde described 2003 in there article, I always missed the deep connection on a team level. Ok we do scale at product owner side, but how we handle topics like architecture, infrastructure, sharing technical knowhow and experiences over all teams?-Spotify describes in there article how they did. And you know what, without knowing it, that was exactly our  implementation at youngculture so far too :-).



  • A Squad is similar to a Scrum Team, designed to feel like a mini-startup
  • A Tribe is a collection of squads that work in related areas
  • A Chapter is your small family of people having similar skills and working within the same general competency area, within the same tribe
  • 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

What I personally like mostly is having instruments like Chapter's and Guild's that makes the glue over all company and share knowhow, tools and code not only but mostly on personals interest.