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 1 – Origins of Agile and Lightweight Methodologies

  1. What makes software development unique from the development of other large, complex products, such as ships, utilities, bridges, roads, or buildings?
    • Software addresses functional business and user needs that are always changing, and modern software development practice supports the evolution of software to address those changing needs.
  2. Why do plan-driven and linear-sequential development practices often fail when developing software?
    • Often referred to as the Waterfall development model, plan-driven and linear-sequential development practices assume customer and end user needs don't change, and that architectures and designs cannot adapt to support the evolving needs.
  3. What are some of the development practices often associated with lightweight and agile-based software development practices?
    • Adaptive Software Development (ASD), Crystal Clear, Extreme Programming (XP), Feature Driven Development (FDD)...