Episode 75 - Squads, Chapters, & Tribes... Oh My!!!

In this episode, Bob and Josh respond to a listener request around our views/implementations of Spotify's agile approach.  Vic (@AgileCoffee) asked specifically about our view on Chapters, so we dig into what they are, how we use them, and how they fit into the whole approach.

What's your view on Spotify's spin on agile?  Do you use any of their techniques?

Bonus Content:
Here is the article Josh mentions that he just wrote about this topic and how Spotify's methods are applied in his company: Why We Spotify'd Our Names

Download this episode

6 comments:

  1. Thanks for answering my questions! I think it's valuable to discuss Spotify's model in relation to the myriad approaches to scaling Scrum out there, too. I've had success with chapters and guilds in a couple orgs, but Dude's maturity with the model is more mature than I've ever gotten.

    Now, about that sticker... :)

    ReplyDelete
    Replies
    1. Glad we could help out. DM @metahyphencast on Twitter and we'll get that sticker shipped out.

      Delete
  2. I am a little late to discovering this, but I had a follow-up question. In this episode you mention that chapter leads are typically your architects. I believe in the standard Spotify model they are the people managers (and technical leads). How do people managers get layered into you approach?

    ReplyDelete
    Replies
    1. We have 3 primary areas of focus across our tribe (people, process, & product). Our managers focus on building great people and teams while architects focus on building great products. That's why we have our architect-level focus be chapter "leads". We know it is different, but it works best for us like this.

      That's not to say that managers aren't involved in the chapters, but it is not their primary area of focus. Make sense?

      Delete
    2. Thanks for the reply. Are your managers technical? Are they part of the squads as well?

      Delete
    3. They are technical, but not part of the squad. We prefer to keep squad members focused only on sprint work. Anyone with priorities other than the sprint goal is not a part of the squad for us.

      Delete