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)
Section 1: Scaling Lightweight Scrum into a Heavyweight Contender
Section 2: Comparative Review of Industry Scaled Agile Approaches
Section 3: Implementation Strategies


In this chapter, you learned how Ken Schwaber, through his company,, implement Scrum scaling practices via their Nexus Framework. The Nexus Framework does not replace the Scrum Framework; rather, it extends Scrum to organize and coordinate the work of three to nine Scrum Teams in order to deliver Integrated Increments of value across each planned Sprint.

You have learned that Nexus modifies one artifact, adds two additional artifacts, adds five new events, and adds one new role. Artifacts provide transparency to help avoid bad decision-making from having bad information. Events guide the flow of work across each Sprint. The roles define the responsibilities of the Nexus integration and Scrum Teams.

As with Scrum, there is only one Product backlog for the entire Nexus, from which all the underlying Scrum Teams pull work. Since there is only one only Product backlog, there is one Product Owner who is ultimately accountable for the value that's identified...