You're reading from Driving DevOps with Value Stream Management Improve IT value stream delivery with a proven VSM methodology to compete in the digital economy

Product type Paperback

Published in Aug 2021

Publisher Packt

ISBN-13 9781801078061

Length 676 pages

Edition 1st Edition

Tools

Scrum

Concepts

Agile

Author (1):

Cecil 'Gary' Rupp

View More author details

Table of Contents (23) Chapters

Preface

1. Section 1:Value Delivery

2. Chapter 1: Delivering Customer-Centric Value FREE CHAPTER

3. Chapter 2: Building On a Lean-Agile Foundation

4. Chapter 3: Analyzing Complex System Interactions

5. Chapter 4: Defining Value Stream Management

6. Chapter 5: Driving Business Value through a DevOps Pipeline

7. Section 2:VSM Methodology

8. Chapter 6: Launching the VSM Initiative (VSM Steps 1-3)

9. Chapter 7: Mapping the Current State (VSM Step 4)

10. Chapter 8: Identifying Lean Metrics (VSM Step 5)

11. Chapter 9: Mapping the Future State (VSM Step 6)

12. Chapter 10: Improving the Lean-Agile Value Delivery Cycle (VSM Steps 7 and 8)

13. Section 3:VSM Tool Vendors and Frameworks

14. Chapter 11: Identifying VSM Tool Types and Capabilities

15. Chapter 12: Introducing the Leading VSM Tool Vendors

16. Chapter 13: Introducing the VSM-DevOps Practice Leaders

17. Chapter 14: Introducing the Enterprise Lean-VSM Practice Leaders

18. Section 4:Applying VSM with DevOps

19. Chapter 15: Defining the Appropriate DevOps Platform Strategy

20. Chapter 16: Transforming Businesses with VSM and DevOps

21. Assessments

22. Other Books You May Enjoy

Identifying value streams

James Martin fundamentally understood why a business organization invests in IT to implement and sustain superior business processes that support its value streams. Martin was ahead of his time, but his ideas persist—for example, The Open Group Architecture Framework (TOGAF) still employs James Martin's value stream concepts in their Business Architecture standard (Open Group Guide, Value Streams, January 2017).

But what exactly did James Martin mean when he employed the term value stream? Martin was not merely looking for ways to improve IT development and operational processes. Instead, his goal was to help organizations restructure their value streams and implement software applications to support, sustain, and continuously improve value delivery across all value streams.

In his book, James Martin cites research from a study published by T. H. Davenport titled Process Innovation, which identified an average of 14 value streams across 5...