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

Leveraging empirical process control theory

Scrum's foundations lie on empiricism, as opposed to following a pre-planned process. Empiricism in the philosophy of science, which emphasizes on knowledge acquisition through hypothesis, theories, experimentation, and the validation of results. For example, the scientific method is based on empiricism.

A hypothesis is an initial – though hopefully testable – assumption, when supporting data or information is lacking, about how or why something works the way it does. In contrast, a theory is an attempt to explain the observed phenomenon based on the data and the facts that are known. Hypothesis and theories both serve as a starting point to assess our understanding of the world around us.

Next, experiments are designed that test the hypothesis or validate whether the theories work. When the evidence supports the hypothesis or theories, the scientists (developers, in the case of Scrum) gain confidence in their understanding...