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

Addressing the pitfalls of DevOps

In this section, you will learn strategies for addressing 18 scenarios that can present a challenge to your DevOps implementation plans. The list is not meant to be an all-inclusive discussion on situations you may face, but it is reasonably comprehensive. As you read through these subsections, begin to think about how you can apply the VSM concepts, methods, and tools you've learned about to discover issues and their root causes, as well as how to improve them.

Let's begin by recognizing and avoiding the consequences of Conway's Law.

Avoiding the pitfalls of Conway's Law

In 1968, Melvin E. Conway wrote an article for the Harvard Business Review (HBR) titled How Do Committees Invent? Unfortunately, HBR rejected it on the grounds that he had not proved his thesis (http://www.melconway.com/Home/Conways_Law.html). However, Conway persisted and submitted the paper to Datamation, who published it in April 1968. His persistence...