Book Image

Driving DevOps with Value Stream Management

By : Cecil 'Gary' Rupp
Book Image

Driving DevOps with Value Stream Management

By: Cecil 'Gary' Rupp

Overview of this book

Value Stream Management (VSM) opens the door to maximizing your DevOps pipeline investments by improving flows and eliminating waste. VSM and DevOps together deliver value stream improvements across enterprises for a competitive advantage in the digital world. Driving DevOps with Value Stream Management provides a comprehensive review and analysis of industry-proven VSM methods and tools to integrate, streamline, and orchestrate activities within a DevOps-oriented value stream. You'll start with an introduction to the concepts of delivering value and understand how VSM methods and tools support improved value delivery from a Lean production perspective. The book covers the complexities of implementing modern CI/CD and DevOps pipelines and then guides you through an eight-step VSM methodology with the help of a use case showing an Agile team's efforts to install a CI/CD pipeline. Free from marketing hype or vendor bias, this book presents the current VSM tool vendors and customer use cases that showcase their products' strengths. As you advance through the book, you'll learn four approaches to implementing a DevOps pipeline and get guidance on choosing the best fit. By the end of this VSM book, you'll be ready to develop and execute a plan to streamline your software delivery pipelines and improve your organization's value stream delivery.
Table of Contents (23 chapters)
1
Section 1:Value Delivery
7
Section 2:VSM Methodology
13
Section 3:VSM Tool Vendors and Frameworks
18
Section 4:Applying VSM with DevOps

Limiting connections

Often, not all elements in a system are connected. The easiest way to reduce system complexity is to reduce the opportunity for elements to communicate or interoperate with one another. Another way is to reduce the number of elements that participate in a system.

If you have studied Scrum or Lean-Agile scaling strategies, you probably noted that they all leverage small team concepts. They do this even on very large product development activities, sometimes involving hundreds or thousands of people. Breaking up work across multiple small teams is one way to limit the number of interactions between the people working on the product.

For example, Scrum of Scrums limits cross-team interactions to a handful of team members, called Ambassadors. The Nexus approach to Scrum implements Network Integration Teams (NITs) to manage cross-team dependencies, coordination, and synchronization activities. Similarly, the Scaled-Agile Framework® (SAFe®) implements...