Value Stream

Most of the time between "idea" and "delivered" is wait time between handoffs. A value stream map shows you exactly where that time is hiding.

A value stream is the end-to-end sequence of activities required to deliver value from a customer need to a customer outcome. It includes everything: discovery, design, development, deployment, and the wait time between each step. The concept comes from lean manufacturing but applies directly to product and software organizations.

The reason value streams matter for organizational design is that they expose where flow breaks down. A value stream map for a web application deployment might show 15.5 hours of actual work time spread across 52 days of elapsed time, a 1.2% work-to-waste ratio. Most of that waste is wait time between handoffs across team boundaries. This is why Team Topologies anchors stream-aligned teams to value streams rather than technical components; you align team boundaries to the flow of value so that handoffs become the exception, not the rule.

Resources

• Value Stream Mapping — the detailed activity for mapping and measuring a value stream
• Flow — the broader principle that value streams help you optimize
• Wardley Mapping — visualizes the value chain and plots components by evolutionary stage
• [[sources/Project to Product|Mik Kersten, Project to Product]] (IT Revolution Press, 2018) — the Flow Framework for measuring value stream health
• Re-aligning Teams to Value Streams — a case study applying value stream alignment to real team structures