SAFe® 5 Lean Portfolio Management Portfolio Kanban & Flow Management 3

Question 1

What typically happens to a Portfolio Epic when its Lean Business Case is rejected during the Analyzing state?

Accepted Answer

It is returned to the Funnel for reconsideration or removed from the Portfolio Kanban

Answer

It is automatically promoted to the Implementing state for a trial run

Answer

It is immediately escalated to the Board of Directors for override

Answer

It is reassigned to a different ART with a larger capacity

Question 2

How does SAFe recommend sequencing Epics in the Portfolio Backlog for implementation?

Accepted Answer

Using Weighted Shortest Job First (WSJF) or similar economic prioritization

Answer

First-in, first-out (FIFO) order based on submission date

Answer

Alphabetically by Epic title for ease of reference

Answer

By the organizational seniority of the Epic's executive sponsor

Question 3

What is the key characteristic that distinguishes a Portfolio Epic from a Program Epic in SAFe?

Accepted Answer

Portfolio Epics have significant strategic, financial, or cross-Value-Stream impact requiring LPM-level approval

Answer

Portfolio Epics are smaller in scope and can be completed within a single Program Increment

Answer

Portfolio Epics can only be implemented by a single ART with no dependencies

Answer

Portfolio Epics are tracked in the team backlog rather than the Portfolio Kanban

Question 4

Which flow metric measures the rate at which Portfolio Epics are completed over a defined time period?

Accepted Answer

Throughput (Flow Velocity)

Answer

Lead Time

Answer

Flow Efficiency

Answer

Work Item Age

Question 5

What does reaching the 'Done' state in the Portfolio Kanban signify in SAFe?

Accepted Answer

The Epic has been fully implemented and its outcomes have been evaluated against expected results

Answer

The Epic has been abandoned due to lack of funding

Answer

All team members assigned to the Epic have been reassigned to new work

Answer

The Epic's budget has been fully exhausted regardless of outcome

Question 6

How should the LPM function handle a Portfolio Epic that requires implementation across multiple Value Streams?

Accepted Answer

Coordinate implementation across affected Value Streams through the LPM function, aligning priorities and dependencies

Answer

Split it into entirely independent Epics per Value Stream with no cross-team coordination

Answer

Assign full ownership to the single largest Value Stream and have others adapt

Answer

Defer it indefinitely until one Value Stream gains enough capacity to handle the full scope alone

Question 7

What is the primary use of a Cumulative Flow Diagram (CFD) in managing the Portfolio Kanban?

Accepted Answer

To visualize Epic flow across Kanban states over time and identify bottlenecks and WIP build-up

Answer

To track individual contributor performance and utilization rates

Answer

To generate quarterly financial forecasts for portfolio budget reviews

Answer

To schedule Program Increment planning sessions across all ARTs