Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Driving DevOps with Value Stream Management

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

Arrow left icon
Product type Paperback
Published in Aug 2021
Publisher Packt
ISBN-13 9781801078061
Length 676 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Cecil 'Gary' Rupp Cecil 'Gary' Rupp
Author Profile Icon Cecil 'Gary' Rupp
Cecil 'Gary' Rupp
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

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

Questions

  1. Why is it not recommended to jump straight into mapping the desired future state of a value stream?
  2. How does value stream mapping differ from process modeling techniques?
  3. Why shouldn’t we automate a business process until we have made improvements to work and information flows?
  4. Once the VSM team, value stream operators, and other critical stakeholders learn Lean processes, is there anything else they should do before executing their VSM plan?
  5. What is the reason for having a standard set of symbols and icons for value stream mapping?
  6. Collectively, what is the purpose of conducting Gemba walks as part of value stream mapping?
  7. What are the three fundamental rules when practicing Gemba?
  8. In which direction do you start to draw your current state map, and why?
  9. In which order does a VSM team implement Lean improvements to a value stream?
  10. What are the eight steps to draw a current state map?
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime