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.
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 delivery as an end-to-end flow for organizing product work and modernization around value creation.
- How deep it goes
- Defines the activity sequence and four independence characteristics, while presenting activities at a high level.
- Examples
- Names price calculation and search services, plus a single-team mobile application, as possible value streams.
- What you can do after
- Evaluate whether a stream supports fast flow by checking domain alignment, outcomes, team autonomy, and independently changeable software.
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.
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 →
Related concepts
- continuous integrationincludes · Continuous integration is a software development practice in which code changes are integrated frequently into a shared codebase and automatically validated.
- 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.
- software development life cycleequivalent to · The software development life cycle is the organized set of activities through which software is planned, specified, designed, built, tested, delivered, operated, and maintained.
- 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.
- releasehas part · A software release is a version or set of changes made available to intended recipients for deployment or use.
- deploymenthas part · Deployment is the process of making software, models, or other computational systems available to operate in a target environment.
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.