liveBook · Manning

Value stream mapping

As explained in 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.

When API design takes too long or documentation and consistency suffer, start by making the delivery workflow visible. Value stream mapping (VSM) traces the activities that fulfill a customer request, including the flow of work and information. Although VSM usually spans high-level organizational processes, its notation can be adapted to map an API delivery process step by step. section 2.14 section 2.4

Build a current-state process map before choosing what to automate:

  • Use observations and collected data to draw the sequence of activities and attach metrics to each step. section 2.4
  • Mark work awaiting processing between steps with inventory triangles. A queue makes potential waste visible. section 2.4.3
  • Add a time ladder: put TT above LT for each block and show the totals for the process. section 2.4.3
  • Use the map to distinguish wasteful activities that might be eliminated from value-adding activities that could be improved. section 2.14

API delivery backlog

In an API delivery workflow tracked with Jira, count the tickets awaiting processing between steps and mark those queues on the map. Compare them with the step-level TT and LT on the time ladder before deciding where an APIOps improvement might help. section 2.4.3 section 2.14

Figure 2.7 Completed Current Conditions and Problem Statement section, showing the process map with metrics
figure

A completed current-conditions map shows the process together with its performance metrics. section 2.4.3

How Automating API Delivery covers it

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 it assumes
Starts with observations and metrics gathered for each process step; requires paper rather than coding.
What you can do after
Practice/perform it by mapping API delivery, marking queues and time metrics, and identifying activities to eliminate or improve.
How it connects
Links value stream mapping to A3 problem-solving, lean thinking, process mapping, and APIOps automation.

Also explained in

Compare how 2 books explain value stream mapping →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.