The History and Evolution of VSM
This domain tests whether you can trace the value stream concept from its manufacturing origins to modern software delivery, and explain why each step in that evolution happened. Expect questions on the key sources, on the shift from project to product thinking, and on how VSM differs from a value chain or a business process.
Lean origins
The idea entered management literature through lean manufacturing. Womack and Jones, in Lean Thinking (1996), defined the value stream as the set of all the specific actions required to bring a specific product through three critical management tasks: problem solving, information management, and physical transformation. Rother and Shook's Learning to See (1999) turned that definition into a working method, using current-state and future-state maps with a timeline ladder that exposes waiting time between process boxes. The Toyota Production System supplied the underlying logic: takt, pull, and the relentless removal of waste.
From the shop floor to the office and to software
Karen Martin and Mike Osterling extended mapping to office and service work (2014), where the inventory being counted is queues of emails, tickets, and decisions rather than pallets. Software adopted the same reasoning. The DevOps Handbook's Three Ways put flow first; Mik Kersten's Project to Product (2018) argued for funding and measuring value streams instead of projects; Team Topologies (Skelton and Pais, 2019) made the value stream-aligned team an organizational building block; and DORA's research connected flow outcomes to delivery and organizational performance.
Worked example
A payments team claims its 40-day lead time is a DevOps problem and proposes faster CI. Tracing the concept back to Rother and Shook's timeline ladder shows the reasoning error: lead time belongs to the whole chain, not the build stage. The 40 days are 5 days of design, 10 days waiting for a sprint slot, 3 days coding, 15 days in a release queue, and 7 days of manual verification. Thirty-two of the forty days are wait, so the leverage is in batching and approval policy upstream, not in build speed.
Traps that cost marks
- Confusing a value stream with Porter's value chain (an industry-level model) or with a department or process.
- Believing VSM is manufacturing-only, or that it began with DevOps.
- Treating the completed map as the deliverable rather than the improvement work it triggers.