Software value stream

Two paths deserve attention

The main value stream is the normal path for features, fixes, and other planned changes. It begins with a request and ends with a result that a customer or another part of the organization can use. Its elapsed time includes active work and waiting.

The recovery value stream is the path for urgent fixes after a production problem. It consumes capacity that may otherwise support planned work. Measuring only planned delivery can make a team look more available than it is.

Map the stages before choosing a metric

Name the start and end events, then list the stages between them. A typical path might include clarification, implementation, review, validation, deployment, and observation. Record queues, handoffs, rework, and external dependencies. A value stream map is useful when it reflects what actually happens rather than the process a team wishes it followed.

Cycle time, flow efficiency, throughput, and rework can then be tied to a stage. Compare similar work and preserve the work type in the analysis. A database migration and a small copy change do not have the same risk or path.

How Weave can help

Weave can connect a value stream question to pull requests, review events, code output, and quality signals. If changes are spending longer in review, the team can inspect queue age, reviewer coverage, change size, and findings instead of guessing from total elapsed time. Deployment and incident records complete the view when the question includes production outcomes.