What triggers the need for a Value Stream?

In SAFe, Value Streams are triggered by Epic requests. Epics are large initiatives that typically span multiple Program Increments and require significant investment. When an Epic is approved through Portfolio Kanban, it triggers the identification or creation of Value Streams to deliver the value. Value Streams represent the series of steps used to deliver value from concept to customer, and Epics are the portfolio-level initiatives that drive their formation or modification.

A. Spike request - Spikes are short-term investigations at team level, too small to trigger Value Streams.

C. User Story request - User Stories are team-level work items, far too granular to establish Value Streams.

D. Feature request - Features are program-level capabilities delivered in single PIs, insufficient scope for Value Stream creation.

1. Scaled Agile Framework official documentation, "Portfolio SAFe", Section: Epic-to-Value Stream Flow, scaledagileframework.com/portfolio-safe/

2. Leffingwell, D. (2018). "SAFe 4.5 Reference Guide", Chapter 3: Portfolio Level, pp. 89-92, Addison-Wesley Professional

3. Scaled Agile, Inc. "Portfolio Kanban", Section: Epic Analysis and Approval, scaledagileframework.com/portfolio-kanban/

4. SAFe 5.0 Distilled (2020), Chapter 7: Portfolio SAFe, Section: Connecting Epics to Value Streams, pp. 145-148

5. Scaled Agile Framework, "Value Streams", Section: Identifying Value Streams, scaledagileframework.com/value-streams/