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 5: Driving Business Value through a DevOps Pipeline

  1. DevOps began as a collaboration strategy in the context of Agile Systems Administration. The initial goal was to improve communications and collaborations between development and operations teams within an IT organization. Ultimately, CI/CD pipelines address the issues of mismatched velocities between development and operations teams.
  2. Configuration Management, Task Management/Automation, Containerization
  3. CI enforces a discipline of merging all developers' working copies of their code to a shared repository several times a day.

    The purpose is to verify each incremental code integration's functionality through software build and test processes as and when the code is developed.

    The goal is to ensure the main software code is always working and in a potentially deployable state.

  4. Software developers thrive in a world of change, delivering new features and capabilities continuously. That's a...