Value Streams Inventory and Attributes - Understand the relationship between the Value Streams Inventory and the Value Stream Stages Inventory
Value Streams Inventory and Attributes
Chapter 37. Understand the relationship between the Value Streams Inventory and the Value Stream Stages Inventory
Executive Summary: Chapter Overview
IF4ITThe Bottom Line
Core Concepts
| Concept | Definition & Strategic Role |
|---|---|
| Stages as Attributes | The simpler approach used in this document, where ordered stages are captured within the Value Stream record. |
| Stages as Inventory Records | A more granular model in which each stage has its own identifier, attributes, relationships, and governance. |
| Granularity Trade-Off | Enterprises choose between simplicity and stage-level precision based on analysis, governance, and measurement needs. |
Quick Q&A
Question: When should an enterprise create a separate Value Stream Stages Inventory?
Read More Below
In this version of the Value Streams Inventory, the stages of a value stream are captured as an ordered descriptive attribute — the Value Stream Stages attribute — and the Capabilities that enable a value stream are related to the value stream as a whole. For many enterprises this is sufficient. It records the structure of each value stream and the Capabilities each flow depends on, and it supports analysis of value delivery at the level of the whole value stream.
Some enterprises need finer resolution. They need to know which Capabilities enable which individual stage — so that they can perform pinpoint impact analysis when a single Capability degrades, diagnose precisely which stage of a flow is the bottleneck, or make investment decisions at the level of an individual stage. For these enterprises, the value stream’s stages are broken out into a separate inventory, in which each stage becomes a governed Noun Instance in its own right — with its own identifier, its own descriptive attributes, and Capabilities related directly to it.
When stages are governed in a separate inventory, the relationship between a value stream and its Capabilities does not disappear — it becomes more granular. Capabilities are related directly to individual stages, and the value-stream-level set of enabling Capabilities becomes a derived value, computed as the union of the Capabilities that enable each of the value stream’s stages. This is a deliberate trade-off. The stages-as-attribute approach in this document is simpler, faster to populate, and sufficient for whole-value-stream analysis. A dedicated stages inventory is more granular and supports finer per-stage analysis, at the cost of a second inventory to build and govern. Whether to make that move is a decision each enterprise makes according to its own analytical needs.
The IF4IT recognizes the Value Stream Stage as an anticipated Noun Type in the Enterprise Inventory Management taxonomy. Should it prove valuable to standardize the practice, the IF4IT may publish a companion Value Stream Stages Inventory and Attributes document. Until then, enterprises that choose to govern stages as first-class entities should do so following the general inventory governance principles in the IF4IT Enterprise Inventory Management Best Practices document.
How to cite this page
When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.
Example (informal web citation):
The International Foundation for Information Technology (IF4IT), LLC. Understand the relationship between the Value Streams Inventory and the Value Stream Stages Inventory | Value Streams Inventory and Attributes. https://if4it.org/best-practices/value-streams-inventory-and-attributes/understand-the-relationship-between-the-value-streams-inventory-and-the-value-stream-stages-inventory/ (accessed 2026-07-28).
See About Us for content governance and site-wide citation guidance.
Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present
Legal Disclaimers