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

Conducting a Nexus Sprint

A Sprint within Nexus is very similar to the traditional Scrum Sprint. There is one additional event: the Daily Nexus Scrum. Also, modifications are made to the Sprint review and Sprint retrospective events. For example, there is only one Sprint review for the Nexus. The reason for this is that the product must be viewed as a whole solution, and not individual parts.

Sprint retrospectives are a bit more complex in that there are Nexus retrospectives scheduled both before and after each Scrum Team conducts their retrospectives. The reason for this is that the NIT and select members from the Scrum Teams meet initially to review dependency and integration issues that have impacted or more of the Scrum Teams. These assessments go back to the effected Scrum Teams for their consideration during their Sprint retrospectives. The Scrum team retrospectives will likely result in cross-team actions that must be taken back to the Nexus to consider and implement.