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

Implementing Scrum Artifacts

By definition, the term artifact refers to any object made by humans or something that can be observed through investigations or experimentation. In the traditional model, we are used to having an untold number of potential artifacts related to a project. Many of those artifacts take the form of physical documentation and reports of various topics. However, in a generic sense, a programmer's code and database schemas are other examples of artifacts. In the traditional model, documentation is a direct result of the detailed project planning, monitoring, and control processes.

Scrum seeks to minimize the production of artifacts, and Sutherland and Schwaber limited their list of artifacts to just three. These include the Product Backlog, Sprint Backlog, and Increments. Collectively, these artifacts portray the work and value of a project and provide the means for transparency, inspection, and adaption. The goal is to keep the team's focus strictly...