A Practical Guide to Distributed Scrum

This content is syndicated from Agility@Scale: Strategies for Scaling Agile Software Development by ScottAmbler. To view the original post in full, click here.

I'm happy to announce that A Practical Guide to Distributed Scrum by Elizabeth Woodward, Steffan Surdek, and Matthew Ganis is now in print.  I've been talking this book up in presentations and with customers the past few months and promised that I would let everyone know once it was available.  I was one of several people who wrote forewords for the book, Ken Schwaber, Roman Pichler, and Matthew Wang also did so, and I've modified my foreword below to help you to understand a bit better what the book is about.

If you're thinking about buying this book, you're probably trying to answer one or more of the following questions: "What will I learn?", "Should I spend my hard earned money on this book?", "Will it be worth my valuable time to read it?", and "Is this a book that I'll refer to again and again?" To help you answer these questions, I thought I'd list a few user stories which I believe this book clearly fulfills:
As a reader I want:

  • a book that is well-written and understandable
    real-world examples that I can relate to
  • quotes from actual people doing this in the field
  • to understand the challenges that I'll face with distributed agile development

As someone new to agile I want to:
  • learn the fundamentals of Scrum
  • understand the fundamentals of agile delivery
  • learn about what actually works in practice
  • discover how extend Scrum into an agile delivery process

As an experienced agile practitioner I want to learn:
  • how to scale agile approaches for distributed teams
  • how to overcome the challenges faced by distributed teams
  • how to tailor existing agile practices to reflect the realities of distribution
  • bout "new" agile practices which we might need to adopt
  • techniques so that distributed team members can communicate effectively
  • how to extend Scrum with proven techniques from Extreme Programming, Agile Modeling, and other agile methods
  • how to address architectural issues on a distributed agile team
  • how agile teams address documentation
  • how agile teams can interact effectively with non-agile teams

As a Scrum Master I want to learn how to:
  • lead a distributed agile team
  • facilitate a distributed "Scrum of Scrums"
  • facilitate the successful initiation of a distributed agile project
  • facilitate communication and collaboration between distributed team members

As a Product Owner I want to learn:
  • how to manage a product backlog on a distributed team
  • about different categories of stakeholders whom I will need to represent
  • about techniques to understand and capture the goals of those stakeholders
  • how to manage requirements with other product owners on other sub-teams
  • what to do during an end-of-sprint review
  • how I can streamline things for the delivery team that I'm working with

As an agile skeptic I want to:
  • see examples of how agile works in practice
  • hear about the challenges faced by agile teams
  • hear about where agile strategies don't work well and what to do about it

I work with organizations around the world helping them to scale agile strategies to meet their real-world needs. Although this book is focused on providing strategies for dealing with geographical distribution, it also covers many of the issues that you'll run into with large teams, complex problem domains and complex technical domains. An important aspect of scaling agile techniques is to first recognize that's there's more to scalability than dealing with large teams, something which this book clearly demonstrates.

At the risk of sounding a bit corny, I've eagerly awaited the publication of this book for some time. I've known two of the authors, Elizabeth and Matt, for several years and have had the pleasure of working with them and learning from them as a result. Along with hundreds of other IBMers I watched this book get written and provided input where I could.  The reason why I'm so excited about it is that I've wanted something that I could refer the customers to that I work with and honestly say, "yes, we know that this works because this is what we do in practice".

IBM is doing some very interesting work when it comes to scaling agile. We haven't published enough externally, in my opinion, due to a preference for actively sharing our experiences internally. This book collects many of our experiences into a coherent whole and more importantly shares them outside the IBM process ecosystem. Bottom line is that I think that you'll get a lot out of this book.

Related Reading:

Leave a Reply

Your email address will not be published. Required fields are marked *

five × two =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”



To explore how we can help you, please get in touch