Ignites - Value Stream Mapping & Analysis
summary
A quick, data-first rundown: a mapped pipeline reveals 100 items in 90 days piled into queues, with value-add 16% and non-value 63%, and a monthly deployment bottleneck that clamps flow. The actionable claim is clear — reduce WIP and queues, break deployment into smaller batches, measure with a cumulative flow diagram, and target the bottleneck first; value stream mapping is the diagnostic tool, not the fix.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:44What is Value Stream Mapping?
- 0:59Value Stream Vocabulary (3)
- 1:44Value Add vs. Non Value Add
- 2:14Why Value Stream Mapping?
- 2:29Identify your Process Activities
- 2:59Add Time Data (2)
- 3:29Add Calculations and Identify Bottleneck (2)
- 3:59VSM Rules of Thumb (2)
related talks
30mMake Your Value Stream Network Visible
21mAgile: After the Value Stream
30mThe Case for Value Stream Architecture
54mValue Streams, Quality Engineering And You
28mThe DevOps Pipeline
02h 23mUsing VS Mapping to Implement DevOps
47mMap and Measure your way to Performance
24mAre You Really Delivering Customer Value?
