Guess what – I’ve updated Scrum and XP from the Trenches!
Eight years have passed, and this book is still really popular. Wow! I never could have imagined the impact this little book would make! I still bump into teams, managers, coaches, and trainers all over the place that use it as their primary guide to agile software development.
But the thing is, I’ve learned lots since 2007! So the book really needed an update.
Since publishing the book, I’ve had the opportunity to work with many agile and lean thought leaders; some have even become like personal mentors to me. Special thanks to Jeff Sutherland, Mary and Tom Poppendieck, Jerry Weinberg, Alistair Cockburn, Kent Beck, Ron Jeffries, and Jeff Patton – I can’t imagine a better group of advisors!
I’ve also had the chance to help a lot of companies implement these ideas in practice: companies in crisis as well as super-successful companies that want to get even better. All in all, it’s been a pretty mind-blowing journey!
When I reread this old book, I’m surprised by how many things I still agree with. But there are also some pages that I’d like to rip out and say “What the *&€# was I thinking? Don’t do it like that! There’s a much better way!”
Since the book is a real-life case study, I can’t change the story. What happened is what happened. But I can comment on it!
So that’s what the second edition is – an annotated version of the original book. Like a director’s cut. Think of it as me standing behind your shoulder as you read the book, commenting on stuff, cheering you on, with the occasional laugh and groan.
Here it is. Spread the word.
You know the saying “don’t shoot the messenger”? Well, that goes both ways – “don’t praise the messenger”. Well, OK, you can shoot or praise the messenger for the quality of the delivery – but not for the message content!
I’ve spent a few years working with Spotify and published a few things that have gained a surprizing amount of attention – especially the scaling agile article and spotify engineering culture video. This has come to be known as the “Spotify Model” in the agile world, although it wasn’t actually intended to be a generic framework or “model” at all. it’s just an example of how one company works. The reason why I shared this material is because my Spotify colleagues encouraged me to, and because, well, that’s what I do – help companies improve, by learning stuff and spreading knowledge.
Since then, many companies have been “copying” the Spotify model, which I found rather scary at first. But now I’ve met quite a number of those companies (and heard back from even more), and so far I have yet to see a case where a company ended up in a worse position than where they were. In fact, some have seen some huge improvements! Pretty surprising actually. So apparently, yes, companies can copy models from each other, and it can sometimes be helpful – mainly because it’s almost always valuable to look at your own organization and process with a critical eye, and take inspiration from others. As long as you adapt to your local context (which most do, eventually).
So, back to the messenger thing.
I’ve noticed, via various blogs and articles and presentations, that people sometimes seem to make the assumption that I invented the Spotify model. Well, I most certainly didn’t! I’m just the messenger. Everything I do at Spotify (and other clients) is collaborative. As coach and mentor I have no formal authority, so I have to work with and through other people. The Spotify model is the result of a lot of people collaborating and experimenting over time, and many aspects of the model were invented without my involvement at all. I certainly wouldn’t want to take credit from the people involved.
So, if you see or hear anyone making the claim that I invented the model, please point out that I didn’t, and refer them to this blog if there are any doubts.