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

Delaying decisions and commitments

The Lean concept behind this principle is that decision-making should never be rushed. In fact, you should wait until that last practical moment to make most decisions. This strategy is the exact opposite of what occurs in the traditional waterfall-based software development model. The waterfall model forces project teams to make detailed project plans based on highly uncertain and speculative information. Then, the development team was expected to follow those plans as if they were gospel.

In contrast, Agile-based software development methodologies, such as Scrum, recognize that markets change and that customer needs to evolve over time. Given those facts, if we make decisions early, it's very likely they will be wrong. The more uncertain the market or the more dynamic the customer environment is, the more likely this statement is true.

Delaying decisions on priorities, the architecture, and system designs until we have better facts on...