Value stream mapping
Value stream mapping is a technique for representing and analyzing the flow of work and information through a process to identify waste and opportunities for improvement.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
Value stream mapping is a technique for visualizing activities, dependencies, delays, and flows across the delivery of value.
- How it is used
- Visualizes delivery steps and bottlenecks to support conversations about organizational improvement and modernization.
- How deep it goes
- Explains what the visualization reveals and how to discuss obstacles, but does not prescribe mapping steps or measurement rules.
- Examples
- Uses broadband customer self-fulfillment, delivery bottlenecks, and a delayed SEO request to make flow and its consequences tangible.
- What you can do after
- Practice/perform collaborative investigation of delivery bottlenecks and use the resulting map to communicate a modernization obstacle.
Automating API Delivery
Value stream mapping is a lean analysis technique that visualizes the flow of work and information through a process to identify waste and improvement opportunities.
- How it is used
- Visualizes API delivery work to identify waste and guide APIOps improvement choices.
- How deep it goes
- Walks through process-level mapping, queues, and a TT/LT time ladder; defers broader applications of VSM.
- Examples
- Uses Jira ticket backlogs and a completed current-conditions map with process metrics.
- What you can do after
- Practice/perform it by mapping API delivery, marking queues and time metrics, and identifying activities to eliminate or improve.
Read how Automating API Delivery explains value stream mapping →
Build High Value Software Systems
A Lean technique for representing and analyzing the flow of work through a value stream.
- How it is used
- Locates delays in software delivery streams and end-to-end request paths so improvements target actual flow rather than formal process diagrams.
- How deep it goes
- Develops maps through timestamps, time and queue metrics, component latency breakdowns, and a constraint-to-countermeasure redesign example.
- Examples
- Uses a three-hour feature delayed over eight days, a checkout latency breakdown, and a redesign of twice-weekly requirements breakdown.
- What you can do after
- Diagnose/debug with it by finding consequential waits, then evaluate a countermeasure against delivery lead time or user-visible latency.
Read how Build High Value Software Systems explains value stream mapping →
Also covered in
What to know first
- lead timeLead time is the elapsed time from when work is initiated or becomes available until its result is completed, delivered, or made available to its recipient.
- operating modelAn operating model is the arrangement of structures, processes, responsibilities, practices, and capabilities through which an organization or system performs and manages its work.
- dependencyA dependency is a component, resource, or prerequisite that another software component or activity relies on to function, build, or proceed.
- value streamA value stream is the complete sequence of activities, decisions, handoffs, and information flows through which work creates and delivers value to a customer or user.
Related concepts
- distributed tracing systemuses · A distributed tracing system is software that records and correlates an operation’s execution across distributed components, including its path and timing.
- onboardinguses · Onboarding is the process of helping a newcomer become familiar with and able to participate in a product, team, organization, or system.
- memory bounduses · A workload is memory-bound when its performance is limited primarily by memory access or data-transfer capacity rather than computational throughput.
- platform engineeringmeasures · Platform engineering is the discipline of designing and operating internal platforms that provide software teams with reusable capabilities and self-service workflows.
- process mapused by · A process map is a visual representation of the activities, queues, delays, and handoffs in a process.
Questions about value stream mapping
What is value stream mapping?
Value stream mapping is a technique for representing and analyzing the flow of work and information through a process to identify waste and opportunities for improvement.
Which Manning books explain value stream mapping?
Architecture Modernization: Socio-technical alignment of software, strategy, and structure, Automating API Delivery and Build High Value Software Systems.
What should I know before learning value stream mapping?
Manning books that teach value stream mapping usually introduce lead time, operating model, dependency and value stream first.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.


