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

Dealing with creative versus repeatable pipeline activities

One of the challenges with improving value stream deliveries is the challenges associated with automating or even estimating the scope of work involved in concept ideation, requirements definition, and analysis. In software development, we refer to this stage as the Fuzzy Frontend.

This term was originally coined by Peter Koen, a professor at the Stevens Institute of Technology. It refers to the value stream activities associated with creating new product ideas and concepts that need to be analyzed to determine customer fit and commercial viability.

Some of these activities are controlled by the product management or product owner function. This is because they alone have the responsibility of deciding what goes into a product and what does not. But the development teams are also involved as they must assess the difficulty and time required to implement each new requirement. In Agile, we refer to assessing requirements...