Achieving Business Agility with Value Stream Management
summary
Argues that improving business agility requires shrinking delays across the workflow using Theory of Constraints, flow theories and Lean thinking and gives concrete practices: use minimum business increment slices instead of timeboxed MVPs, apply WIP limits and reduced batch size to cut feedback latency, measure that 96% of errors come from the system not people, map value streams with an idealized value stream app rather than expensive mapping, and include test‑first automation, portfolio investment pillars and MBIs to deliver consumable value faster.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 4:07Systems
- 6:37Inherent Problem
- 9:00System Management
- 10:37Silos
- 13:24Information
- 14:36Delays Waste
- 16:00Unplanned Work
- 16:34Global Level
- 18:34Avoid Value Stream Crossing
- 18:54Value Creation Structure
- 19:37MVPs
- 20:20Minimum Business Increment
- 21:30Value Increment
- 22:32Summary
- 27:14Scrum
- 28:09Structure
- 29:13Team Structure
- 29:48Frameworks dont work
- 30:06Value Stream Mapping creates visibility
- 31:03Poor Value Stream
- 31:26Kanban Bars
- 32:35Identify Value Stream
- 32:59QA
- 39:54Value Stream
related talks
21mAgile: After the Value Stream
51mThe Foundations of Business Agility
15mDelivering value agility in a large company
15mOptimizing the engineering value stream
45mThe recipe for enterprise agility
02h 23mUsing VS Mapping to Implement DevOps
51mMastering Trade-offs for Scaled Agile Success
51mAgility at Scale: A Meeting of Mindsets