Make Your Value Stream Network Visible
summary
Claims the number one barrier to flow is the hidden value stream network, not teams or code, showing a concrete example where a customer-request sits 46 weeks while developers report ~5–10 days of hands-on work. Uses Gephi dynamic graphs and node/edge models (node = team, edge = dependency) plus projected flow time to expose where WIP, sequencing and dependencies concentrate. Finds QAS/Pluto/Falkor-style hubs inflate delivery (160 days in examples), notes 35–50% of orgs lack six‑month capacity, and recommends measuring customer-valued slices, track dependencies, and sequence fastest value first.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:18Value stream explained
- 2:28Customer delivery time
- 4:18Tracking work levels
- 6:47Complexity in large companies
- 8:11Lean and DevOps lifecycle
- 10:25Elite story delivery problem
- 11:55Software mirrors manufacturing
- 13:02Value stream network concept
- 14:52Entropy in organizational flow
- 15:58Demand vs delivery capacity
- 16:45Graph theory for flow
- 19:40Measuring flow time
- 21:26Dynamic flow graphs
- 22:10Visibility improvement tips
- 26:19Summary
related talks
31mHow Value Stream Networks Will Transform IT and Business
06mIgnites - Value Stream Mapping & Analysis
54mValue Streams, Quality Engineering And You
21mAgile: After the Value Stream
29mFlow Engineering - boost velocity, quality & happiness
47mMap and Measure your way to Performance
33mCI/CD is just the Beginning: Optimize Value Creation with Flow Framework
28mThe DevOps Pipeline