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

Chapter 7 – Scrum of Scrums

  1. What is the purpose of Scrum of Scrums (SOS)?
    • To minimally extend the underlying Scrum Framework in order to manage large product dependency, coordination, and integration issues, across multiple teams, with negligible overhead and complexity.
  2. What are the two typical approaches taken to scaling Scrum in the original Scrum model?
    • Bottom up-led by engineering/developers
    • Top down-led by executive management
  3. In the context of an innovation's adoption curve applied to Scrum, what stage is Agile adoption within the software industry?
    • Early to late majority stage
  4. Why did software engineers and consultants largely lead the movement to promote agile practices?
    • They too often received most of the blame for failures caused by strict adherence to the traditional waterfall-based development model
  5. What does it mean to prioritize Product Backlog items in terms of highest value?
    • Development priority goes to those items with the highest customer...