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

Chapter 3: Analyzing Complex System Interactions

IT organizations represent complex systems on several levels. First, the process of software development is a system, as are the operations and support functions. Second, the inclusion of team members extends the software development system's complexity, as does their computing equipment, networks, tools, and software applications.

Suppose the IT department supports multiple Agile or DevOps development teams working on a single product. In that case, each product team would function as both an independent system and as a component of a more extensive system – a "team of teams." In these scenarios, all the teams must collaborate to support the ongoing development of the software product or digitally-enabled service. This chapter provides guidance on assessing the complexity of these (and any other types of systems) by evaluating the elements that make up the system, their connections, and types of interactions...