Book Image

Scaling Scrum Across Modern Enterprises

By : Cecil 'Gary' Rupp
Book Image

Scaling Scrum Across Modern Enterprises

By: Cecil 'Gary' Rupp

Overview of this book

Scaled Scrum and Lean-Agile practices provide essential strategies to address large and complex product development challenges not addressed in traditional Scrum. This Scrum/ Lean-Agile handbook provides a comprehensive review and analysis of industry-proven scaling strategies that enable business agility on an enterprise scale. Free of marketing hype or vendor bias, this book helps you decide which practices best fit your situation. You'll start with an introduction to Scrum as a lightweight software development framework and then explore common approaches to scaling it for more complex development scenarios. The book will then guide you through systems theory, lean development, and the application of holistic thinking to more complex software and system development activities. Throughout, you'll learn how to support multiple teams working in collaboration to develop large and complex products and explore how to manage cross-team integration, dependency, and synchronization issues. Later, you'll learn how to improve enterprise operational efficiency across value creation and value delivery activities, before discovering how to align product portfolio investments with corporate strategies. By the end of this Scrum book, you and your product teams will be able to get the most value out of Agile at scale, even in complex cyber-physical system development environments.
Table of Contents (20 chapters)
1
Section 1: Scaling Lightweight Scrum into a Heavyweight Contender
8
Section 2: Comparative Review of Industry Scaled Agile Approaches
16
Section 3: Implementation Strategies

Scaling SoS

There are development organizations that claim to have more than one product and more than one Product Owner in their Scrum of Scrums. Such a practice is not consistent with the basic principles of Scrum, that is, that multiple teams pull from the same Product Backlog and only one Product Owner can be responsible for the items included and their priorities.

As a basic rule, when you have multiple large products requiring multiple Scrum teams, create multiple Scrum of Scrums—with one SoS for each product. Each SoS has one Product Owner, one Product Backlog, and up to nine development teams. Still, large organizations often have products that are so large that a single Scrum of Scrums is not adequate to handle the organization's development objectives. Recall that an SoS is limited to no more than nine Scrum teams, each having no more than nine members. Ergo, a Scrum of Scrums can have no more than 81 people involved in development. So, what's the organization...