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

Building in quality

Quality has to be built in. By the time you inspect something for quality, it's too late. Whatever quality was built into the product is the quality it will have. If that level of quality is unsatisfactory, the organization has no choice but to scrap the work or repair or rework the defective deliverables. Defects cost money and time and are a prime example of non-value-added waste. No customer wants to pay for those activities.

SAFe further breaks quality down into five dimensions: flow, architecture and design, code, system, and release. SAFe also employs the testing concepts you learned in previous chapters, such as TDD, the use of acceptance criteria, and BDD. For more information on SAFe's concepts to incorporate quality, please visit