VSM Foundation study materials
VSM Foundation study resources

VSM Foundation case studies

VSM Foundation · Put your knowledge to work in context.

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 case studies are 5 cases and about 3,178 words.

1

The Bank That Found 41 Value Streams

Northbridge Bank has 1,100 IT staff organized into nine delivery departments. Its new value stream management lead is asked for a value stream inventory in six weeks.

678 words, about 3 min
2

The 18-Minute Lead Time and the 11-Week Promise

FreshCart, an online grocery with 300 engineers and 40 deployable services, reports median commit-to-deploy lead time of 18 minutes, 60 deployments per day, change failure rate 2%, and MTTR 45 minutes. Its product director says a typical customer-visible change still takes 11 weeks from accepted idea to production, with 70% of the elapsed time waiting for prioritization or legal review.

695 words, about 3 min
3

Traceability Across Three CI Systems and a CAB

Helios Insurance has grown by acquisition. It runs three CI systems, four ticketing tools, two observability stacks, and a ServiceNow change process.

577 words, about 3 min
4

The 38-Day Map Built from Memory

CarePath, a healthcare SaaS vendor, maps its 'patient intake' value stream in a two-hour workshop with nine people. The map shows 14 steps, 38 days elapsed from signed contract to patient data live, and 4 days of touch time.

635 words, about 3 min
5

The Reorg That Did Not Fix the Platform Queue

TransCargo, a logistics firm with 2,500 employees, reorganized 18 months ago into eight stream-aligned teams and two platform teams. Feature lead time fell 30%, but cross-stream dependencies now consume 45% of team capacity; the platform team has a seven-month backlog; an architecture review board still approves every API change; and funding is annual by project.

593 words, about 3 min