Value stream
A 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.
Build High Value Software Systems
A value stream is the complete sequence of activities and handoffs through which work produces an outcome for a customer or user.
- How it is used
- Makes the end-to-end path from software idea to user benefit visible so teams can find delays hidden by local productivity measures.
- How deep it goes
- Defines the stream, classifies activity, and works through process versus wait time; stops short of prescribing one universal workflow.
- Examples
- Uses a session-timeout fix delayed by review and deployment queues, plus retrospective measures such as backlog waits and review rework.
- What you can do after
- Diagnose/debug with it by mapping handoffs and queues, distinguishing necessary checks from waste, and targeting the constraint delaying user benefit.
Read how Build High Value Software Systems explains value stream →
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
A value stream is a sequence of activities that creates new value, especially from discovering user needs through building and delivering software.
- How it is used
- Frames software architecture and team ownership around the flow from user need to delivered business value.
- How deep it goes
- Defines development value streams and elaborates independence through four characteristics and change coupling, without specifying implementation steps.
- Examples
- Uses price-calculation and search services, a small mobile application, and a feature requiring changes by three teams.
- What you can do after
- Apply it via EventStorming to examine domain boundaries and identify cross-team change coupling that limits independent delivery.
Automating API Delivery
A value stream is the complete sequence of activities and information flows required to create and deliver a product or service.
- How it is used
- Uses value streams to examine waste across API design, governance, building, deployment, and publishing.
- How deep it goes
- Defines the lean principle and interprets a mapped API approval process using lead time, touch time, and activity ratio.
- Examples
- Examines approval of a new API operation with 16 working days of lead time and 5.25 hours of touch time.
- What you can do after
- Evaluate/understand API delivery delays by comparing lead time with touch time on a process map.
Architecting for Autonomy
A value stream is a sequence of activities and decisions that collectively delivers a business outcome or other form of value.
- How it is used
- Uses value streams to locate judgment, assign decision authority, and govern how agentic systems create business outcomes.
- How deep it goes
- Explains value-stream redesign through decision surfaces, authority assignment, escalation, and accountability, while stopping short of infrastructure or model detail.
- Examples
- Uses retail banking and relates the pattern to insurance underwriting, healthcare triage, supply-chain optimization, energy trading, and public-sector case management.
- What you can do after
- Apply it by mapping decision surfaces, assigning authority, defining escalation, and anchoring accountability in business capabilities.
Shipping Go: Develop, deliver, discuss, design, and go again
The connected sequence of activities through which work is transformed into value for a customer.
- How it is used
- Frames software delivery as a customer-feedback loop that transforms requested work into shipped product value.
- How deep it goes
- Explains the flow, feedback loop, automation rationale, and pipeline stages without detailing specific implementation configurations.
- Examples
- Uses the develop-deliver-discuss-design loop and a pipeline that analyzes, builds, and ships committed code.
- What you can do after
- Evaluate/understand how to minimize upfront investment by automating handoffs and learning from customers incrementally.
Read how Shipping Go: Develop, deliver, discuss, design, and go again explains value stream →
What to know first
- backlogA backlog is a collection of pending work items or orders awaiting prioritization, processing, fulfillment, or completion.
- CPU timeCPU time is the amount of processor execution time consumed by a program, process, thread, or computation.
- 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.
Related concepts
- continuous integrationincludes · Continuous integration is a software development practice of frequently integrating changes into a shared codebase and automatically validating them with builds, tests, or other checks.
- independent value streamincludes · An independent value stream is a software development value stream aligned to a business subdomain, owned by one empowered team, and supported by independently deployable capabilities.
- independent service heuristicsmeasured by · Independent service heuristics are a set of heuristics for assessing the independence of a value stream and identifying concerns that may limit its effectiveness.
- deploymenthas part · Deployment is the process of placing or releasing software, models, or configuration into a target environment so they can operate there.
- releasehas part · A software release is a version of software made available for use or deployment, or the act of making that version available.
- software development life cycleequivalent to · The software development life cycle is the organized sequence of activities for planning, creating, testing, delivering, operating, and maintaining software.
Questions about value stream
What is value stream?
A 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.
Which Manning books explain value stream?
Build High Value Software Systems, Architecture Modernization: Socio-technical alignment of software, strategy, and structure, Automating API Delivery, Architecting for Autonomy and Shipping Go: Develop, deliver, discuss, design, and go again.
What should I know before learning value stream?
Manning books that teach value stream usually introduce backlog, CPU time and lead time first.
What kinds of value stream are there?
Kinds of value stream include continuous integration and independent value stream.
What are the parts of value stream?
Value stream includes deployment and release.
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.




