VSM Foundation study materials
VSM Foundation study resources

VSM Foundation study plan

VSM Foundation · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

The history and evolution of VSM & Identifying value streams

  • Explain in your own words how value stream thinking moved from lean manufacturing origins into software delivery, naming at least three distinct eras or influences

  • Define value stream, value stream mapping, and value stream management and write a one-paragraph contrast that distinguishes all three

  • Identify at least five candidate value streams in your own organization and justify each boundary using trigger-to-outcome logic

  • Classify each candidate as primary, supporting, or enabling and record the reasoning

  • List the common failure modes of value stream identification, such as org-chart mapping or technology-based slicing

Your checkpoint

A two-page value stream inventory document containing a timeline of value stream thinking, three definitions in your own words, and 5-8 candidate value streams with type labels and boundary justifications

Week 2

Mapping value streams

  • Build a current-state map for one primary value stream covering trigger, process steps, wait states, handoffs, and systems touched

  • Annotate each step with lead time and process time estimates and compute the activity ratio

  • Mark every handoff and queue on the map and quantify total wait time as a percentage of total lead time

  • Identify the three largest sources of delay and label them by category such as approval, environment, or rework

  • Draw a future-state map that removes or automates at least two of the identified delays

Your checkpoint

A current-state and future-state map pair for one value stream, with a lead time versus process time table showing the activity ratio before and after the proposed changes

Week 3

Connecting DevOps toolchains

  • Inventory the tools used across plan, code, build, test, release, deploy, operate, and monitor for the mapped value stream

  • Draw the data flow between tools and mark every manual re-entry point or integration gap

  • Configure or script at least one automated link, such as commit-to-build or build-to-work-item traceability

  • Define the identifiers that must be consistent across tools so that a single change can be traced end to end

  • Document where tool data is trapped and cannot be queried programmatically

Your checkpoint

A toolchain integration diagram plus a written gap list naming each manual handoff, the tools involved, and the proposed automated connection with its data keys

Week 4

Value stream metrics

  • Define lead time, cycle time, throughput, work in progress, flow efficiency, and change failure rate and state the exact start and stop points you will use for each

  • Select a minimal metric set of no more than six measures and justify each against a decision it informs

  • Extract or estimate real data for one value stream over at least four weeks

  • Compute flow efficiency and Little's Law consistency between WIP, throughput, and cycle time

  • Identify at least two metrics that would create perverse incentives and explain why you excluded them

Your checkpoint

A metrics definition sheet with precise calculation rules plus a dashboard or spreadsheet showing four weeks of actual data for one value stream, including flow efficiency and a Little's Law sanity check

Week 5

Inspecting the value stream

  • Run a structured inspection of the mapped value stream using the metrics from week 4 and record observations separately from interpretations

  • Facilitate a blameless review session with at least three people who do the work and capture their view of the biggest constraint

  • Locate the current constraint and show with data why it, and not another step, limits throughput

  • Distinguish systemic delay from individual performance issues in your findings

  • Rank improvement opportunities by expected lead time reduction and effort

Your checkpoint

A written inspection report containing observations, the identified constraint with supporting data, a prioritized improvement backlog of at least five items, and notes from the facilitated session

Week 6

Inspecting the value stream & Organizing as value streams

  • Compare your value stream structure with the current reporting structure and list every mismatch

  • Design an organizational model where teams own end-to-end value streams, including how platform, enabling, and specialist groups support them

  • Define the roles and decision rights that change under a value stream aligned model

  • Draft a transition approach covering funding, reporting lines, and how existing commitments are honored

  • Anticipate at least three sources of resistance and prepare a response for each

Your checkpoint

An organizational design proposal that maps each team to a value stream, shows the before-and-after structure, and includes a role and decision-rights table plus a resistance response plan

Week 7

Evolving value streams

  • Convert the improvement backlog from week 5 into an ordered evolution roadmap with owners and target dates

  • Define the feedback loop that will re-measure the value stream on a fixed cadence and trigger re-inspection

  • Establish guardrail metrics that must not degrade while lead time improves

  • Design a small experiment to test the highest ranked improvement and define its success threshold in advance

  • Plan how the value stream map itself will be kept current rather than becoming a stale artifact

Your checkpoint

A value stream evolution roadmap with sequenced improvements, owners, dates, guardrail metrics, and a defined experiment with a pre-committed success threshold

Week 8

The history and evolution of VSM & Identifying value streams & Mapping value streams & Connecting DevOps toolchains & Value stream metrics & Inspecting the value stream & Organizing as value streams & Evolving value streams

  • Re-derive the definitions and core concepts of all eight domains from memory and check against your notes

  • Re-run the full exercise end to end on a second, smaller value stream to confirm the method transfers

  • Review every deliverable for gaps and correct at least three weak points

  • Practice explaining the value stream story, from identification through evolution, in a ten-minute narrative

  • Build a personal checklist for future value stream engagements

Your checkpoint

A consolidated capstone portfolio containing all prior deliverables, a second value stream worked end to end, a corrected gap list, and a reusable one-page engagement checklist

Milestones

Week 2: You can explain the difference between a value stream, a process, and a team, and you have a current-state map with quantified lead time and a computed activity ratio

Week 4: You have four weeks of real data for one value stream and can state the exact calculation rule for every metric you report

Week 5: You have identified the constraint with data and produced a prioritized improvement backlog reviewed by people who do the work

Week 6: You can describe the target organizational structure and name the specific decision rights that move from managers to value stream owners

Week 8: You have completed the full method twice, hold a consolidated portfolio, and can deliver the ten-minute value stream narrative without notes