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

Building in quality

In the traditional software development model, quality is a lengthy and arduous process that spans the requirements, design, development, and testing phases. Identified functional and nonfunctional requirements translate into system components and features through the architecture and design activities. The developers create test scenarios and test scripts and identify acceptance criteria that their code must eventually pass. Once the code has been developed, the developers or testers run the tests to see if the code passes. If not, the code is sent back to the developers to debug and fix. Since testing is the last phase of overall development activity before deployment, it's very difficult to find the source of bugs and defects, leading to delays and extra costs. By that time, the software code is too big and too complex to efficiently debug.

Testing incrementally

Under Scrum and Agile processes, the requirements, analysis, design, coding, and testing...