An organization is considering how a new service will be supported when it goes live. There are many teams that will contribute to the support of the service. Which approach should the organization…

Question

Options

• ACreate one value stream for every lifecycle phase of support requests
• BCreate one value stream for the entire set of support activities
• CCreate one value stream for each support team
• DCreate separate value streams for practices, people, tools and suppliers

• A
  7% (2)
• B
  73% (22)
• C
  13% (4)
• D
  7% (2)

Explanation

Option B is correct because a value stream represents the complete, end-to-end sequence of steps needed to deliver value for a specific scenario - in this case, supporting the new service from trigger (e.g., an incident) through to resolution. One unified value stream gives the organization visibility of how work flows across all contributing teams, enabling holistic optimization rather than local tuning.

Why the distractors fail:

• A is wrong because creating a stream per lifecycle phase (e.g., one for logging, one for escalation) fragments the flow - value streams cross lifecycle phases; they are not synonymous with them.
• C is wrong because organizing by team creates silos and hides handoff inefficiencies between teams; value streams are structured around outcomes, not org charts.
• D is wrong because practices, people, tools, and suppliers are components of a value stream, not separate streams in themselves - splitting them apart destroys the flow.

Memory tip: Think of a value stream as a single river carrying work from customer request to delivered value. Splitting it by team (C) or phase (A) turns one river into disconnected puddles - water stops flowing.

No community discussion yet for this question.