(Select 2) What applies to the Portfolio Backlog?

Question

Options

• AThe Portfolio Kanban holds Capabilities that are ready for implementation.
• BPrograms plan PIs so that they exhaust the Portfolio Backlog and only then work on their local
• CIt provides a low-cost holding area for approved Business and Enabler Epics.
• DWSJF is used to prioritize Epics in the Portfolio Backlog.

• A
  2% (1)
• B
  4% (2)
• C
  94% (50)

Explanation

C and D are correct because the Portfolio Backlog serves as a low-cost holding area - epics sit there without incurring development costs until capacity is available - and WSJF (Weighted Shortest Job First) is the standard SAFe mechanism for sequencing those epics based on economic value and urgency.

A is wrong on two counts: it's the Portfolio Kanban (a workflow visualization system), not the Portfolio Backlog, being referenced - and Capabilities belong to the Solution Backlog, not the portfolio level. B is wrong because programs plan PIs against their own Program Backlog (Features), not against exhausting the Portfolio Backlog; the Portfolio Backlog feeds programs incrementally via WSJF pull, not all at once.

Memory tip: Think of the Portfolio Backlog as a bank vault - epics are stored cheaply (C) until the economic prioritization key (WSJF = D) unlocks the next one. Capabilities and Kanban boards live outside the vault.

No community discussion yet for this question.