SAFe uses Kanban to manage flow at the Portfolio Level for the following reasons EXCEPT __________.

Question

Options

• ATo ensure that the analysis and discovery work needed for the items are not time bound.
• BTo ensure that there is visibility and transparency.
• CTo capture all ideas in the funnel.
• DTo limit the number of initiatives under consideration.
• ETo ensure that portfolio items are delivered to the Program or Solution Backlogs every 2 weeks.

• A
  4% (1)
• B
  7% (2)
• C
  7% (2)
• E
  81% (22)

Explanation

Option E is the exception because Portfolio Kanban operates on a continuous flow model, not a fixed cadence. Items move from one Kanban state to the next when they are ready - there is no 2-week delivery heartbeat at the Portfolio level (that fixed cadence belongs to Team Iterations and PI events, not Portfolio Kanban).

Options A through D are all valid reasons SAFe uses Portfolio Kanban: A is correct because Portfolio-level analysis and discovery (e.g., Epic hypothesis development) is deliberately not time-boxed, unlike iterations; B is correct because the Kanban board provides a shared, visible view of all portfolio items and their states; C is correct because the Funnel state is specifically designed to capture all new ideas before any commitment; and D is correct because WIP limits at each Kanban state deliberately constrain the number of initiatives in progress, preventing overload.

Memory tip: Think "Portfolio Kanban = pull, not push." Items advance when ready (pull system), so there's no fixed 2-week push cycle. If you see any answer linking Portfolio Kanban to a time-boxed delivery schedule, that's your exception - time boxes live at the Team and Program levels, not the Portfolio.

No community discussion yet for this question.