VSM Foundation study guide
VSM Foundation · Work through your exam, one topic at a time.
Value Stream Management Foundation℠ is a certification offered by DevOps Institute in partnership with the VSM Consortium, aimed at people who need to understand how value flows from idea to customer in a digital organisation. The premise behind the credential is that value stream management has existed since the dawn of lean, but digital value streams need different treatment: DevOps toolchains now give teams far more opportunity to gain actionable insights and deliver value outcomes to customers. The VSM Foundation study guide has 8 sections and about 3,606 words.
01The 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.
479 words, about 2 min02Identifying Value Streams
This domain tests whether you can find and bound value streams correctly - the right customer, trigger, start, and end - before any mapping begins. Most mapping failures are actually identification failures.
468 words, about 2 min03Mapping Value Streams
This domain tests whether you can build a current-state map that is honest, calculate lead time and flow efficiency from it, and design a future state that addresses the real constraint. A map is built from process boxes with data boxes underneath, inventory or queue triangles between them, push arrows, FIFO lanes, supermarkets and kanban posts, information-flow arrows, and kaizen bursts marking problems.
476 words, about 2 min04Connecting DevOps Toolchains
This domain tests whether you can explain how data moves between DevOps tools to make the value stream visible, and how to keep that data trustworthy enough to act on. A DevOps toolchain is every tool that supports the flow of work from idea to running software and back through feedback: planning and work tracking (Jira, Azure Boards), source control (Git), continuous integration (Jenkins, GitLab CI, GitHub Actions), artifact repositories (Nexus, Artifactory), test automation, deployment and release (Argo CD, Spinnaker), observability (Prometheus, Datadog), incident management (PagerDuty) and service management (ServiceNow).
435 words, about 2 min05Value Stream Metrics
This domain tests whether you can choose flow metrics over resource metrics and compute them correctly, including the arithmetic of Little's Law and the difference between averages and distributions. Lead time runs from the customer's request to delivery of value, including all the waiting.
415 words, about 2 min06Inspecting the Value Stream
This domain tests whether you can read a value stream while it is running: which signals to look at, how often, and how to convert what you see into an action on the constraint. Goldratt's Theory of Constraints gives five focusing steps: identify the constraint, exploit it (get more from it without spending), subordinate everything else to its pace, elevate it (add capacity or remove the need), then repeat - and beware inertia becoming the next constraint.
434 words, about 2 min07Organizing as Value Streams
This domain tests whether you can connect value stream design to organizational design: team boundaries, ownership, cognitive load, and funding. A value stream needs a team, or a small set of teams, that owns it end to end and is long-lived enough to learn.
446 words, about 2 min08Evolving Value Streams
This domain tests whether you treat value stream management as a permanent capability rather than a project: how to run improvement cycles, what to change in what order, and when to redraw the streams themselves. The future-state map is a hypothesis.
453 words, about 2 min