(Select 3) What are three ways to coordinate across Value Streams?

Question

Options

• AMove teams across Value Streams to respond to changing business demands.
• BEstablish Enterprise architecture.
• CEmpower the Value Stream Engineer to coordinate all teams in the Value Stream.
• DApply cadence and synchronization.
• EFund the Portfolio, not the Value Streams.
• FCreate a Portfolio Vision and Roadmap.

• A
  2% (1)
• B
  78% (32)
• C
  12% (5)
• E
  7% (3)

Explanation

B, D, and F are the three correct SAFe mechanisms for coordinating across Value Streams at the Portfolio level. Enterprise Architecture (B) establishes shared technical standards, platforms, and guardrails that all Value Streams must align to, preventing siloed or incompatible solutions. Cadence and synchronization (D) creates predictable rhythms-like Portfolio Syncs and aligned PI boundaries-so Value Streams can coordinate timing and dependencies without ad-hoc management overhead. A Portfolio Vision and Roadmap (F) gives every Value Stream a shared strategic direction, ensuring their work converges on common business outcomes rather than drifting independently.

The distractors fail for these reasons: A is wrong because SAFe strongly favors stable, long-lived teams-shuffling people across Value Streams destroys team dynamics and disrupts flow. C is wrong because there is no "Value Stream Engineer" role in SAFe; coordination is achieved through shared artifacts and events, not a single authority figure. E inverts an actual SAFe principle-the framework says to fund Value Streams, not projects, not to withhold funding from Value Streams in favor of the Portfolio.

Memory tip: Think "ADF" - Architecture sets the rules, Drumbeat (cadence) keeps everyone in sync, Future (Vision/Roadmap) points everyone the same direction. These three work at the Portfolio level without micromanaging teams.

No community discussion yet for this question.