How Flow Works
summary
Argues that self‑service clouds plus continuous delivery change flow by turning organizational bottlenecks into queuing problems and uses queuing theory, value‑stream maps and agent‑based models (NetLogo/C) to prove it. Shows a real value stream with 47 days vs 5 days of actual value, builds simulations comparing waterfall to single‑piece flow that deliver far more cumulative value, and demonstrates that controlling occupancy with WIP limits and reducing batch size shortens cycle time by an order of magnitude; shared test environments often cause the worst queues.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:37Programming in the past 14 years
- 16:15Building systems optimizing for flow
- 18:12Are we real engineers now?
- 19:10Work flows as information through value streams
- 23:58Fun fact
- 25:55Sidebar on generative science
- 27:48The Gini coefficient
- 28:49Back to following the work
- 40:12Using generative science to model the wold of work
- 45:48How flow works
- 49:10Outro
