SAFeĀ® 5 Lean Portfolio Management Portfolio Kanban & Flow Management 1 ā Questions and Answers
Question 1: What is the primary purpose of the Portfolio Kanban system in SAFe 5 Lean Portfolio Management?
- To manage individual team backlogs and sprint planning
- To visualize and limit the flow of Epics from ideation through implementation (Correct answer)
- To replace the Program Increment planning event at scale
- To automate budget allocation across Value Streams
Correct answer: To visualize and limit the flow of Epics from ideation through implementation
The Portfolio Kanban system makes Epic flow visible and applies WIP limits so the LPM team can manage the flow of Epics from ideation through analysis to implementation.
Question 2: Which Portfolio Kanban state holds Epics that have been approved by the LPM team and are waiting to be pulled into implementation?
- Funnel
- Reviewing
- Analyzing
- Portfolio Backlog (Correct answer)
Correct answer: Portfolio Backlog
The Portfolio Backlog holds Epics that have passed through the Lean Business Case review and been approved, making them ready to be sequenced and assigned to ARTs or Value Streams.
Question 3: What does applying WIP limits to the Portfolio Kanban system primarily prevent?
- Teams from creating new user stories
- Starting too many Epics simultaneously, which dilutes focus and slows delivery (Correct answer)
- Business Owners from submitting Epic proposals
- The portfolio from exceeding its annual budget
Correct answer: Starting too many Epics simultaneously, which dilutes focus and slows delivery
WIP limits prevent overloading the system by restricting the number of Epics in progress at any one time, maintaining flow and reducing average lead time.
Question 4: At which point in the Portfolio Kanban must a completed Lean Business Case exist before an Epic can proceed?
- When first entering the Funnel state
- When moving from Reviewing into analysis
- When exiting the Analyzing state for approval (Correct answer)
- When being closed in the Done state
Correct answer: When exiting the Analyzing state for approval
The Lean Business Case is the key artifact produced during the Analyzing state; it must be completed before the LPM team can make a go/no-go funding decision.
Question 5: Which principle from Lean thinking explains why limiting WIP in Portfolio Kanban reduces average Epic lead time?
- The Theory of Constraints
- Little's Law (Correct answer)
- The Pareto Principle
- Kaizen Continuous Improvement
Correct answer: Little's Law
Little's Law states that Lead Time = WIP / Throughput, so reducing WIP directly shortens average lead time when throughput remains constant.
Question 6: Which flow metric measures the total elapsed time from when a Portfolio Epic enters the Funnel to when it reaches the Done state?
- Throughput
- Flow Efficiency
- Lead Time (Correct answer)
- Flow Distribution
Correct answer: Lead Time
Lead Time (or Flow Time) measures the end-to-end duration for an Epic to travel through the entire Portfolio Kanban, from identification to completion.
Question 7: What is the primary criterion that triggers a Portfolio Epic's transition from the Funnel to the Reviewing state?
- The Epic has a fully approved and allocated budget
- The LPM team determines the Epic is worthy of further analysis (Correct answer)
- The Epic has already been partially implemented by an ART
- The Epic's return on investment has been formally calculated
Correct answer: The LPM team determines the Epic is worthy of further analysis
The Funnel-to-Reviewing transition occurs when the LPM team agrees an Epic has enough strategic merit to warrant a deeper investigation and Lean Business Case development.
SAFeĀ® 5 Lean Portfolio Management Portfolio Kanban & Flow Management 1
What is the primary purpose of the Portfolio Kanban system in SAFe 5 Lean Portfolio Management?