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

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

Chapter 5: Driving Business Value through a DevOps Pipeline

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.
Configuration Management, Task Management/Automation, Containerization
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.
Software developers thrive in a world of change, delivering new features and capabilities continuously. That's a...