SAFe-Agilist Exploring Lean Portfolio Management Practice Question
A Lean Portfolio Management team is struggling with high Work in Process (WIP) at the Portfolio Kanban level. What is the most effective way to resolve this bottleneck?
⚠ Common exam trap
Candidates often think that handling high WIP requires hiring more staff or increasing team velocity, rather than tightening governance rules to restrict active intake.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Lower the WIP limits for the 'Review' and 'Analysis' states on the Portfolio Kanban.
High WIP at the Portfolio level indicates that the organization is initiating more work than it can feasibly complete, leading to context switching and delays. By enforcing stricter WIP limits at the 'Review' and 'Analysis' states of the Kanban, the portfolio ensures that only the highest-value items are processed. This forces the organization to finish existing epics before starting new ones, maximizing throughput and overall portfolio flow.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the capacity of the Portfolio team to handle all incoming Epic requests.
Why it's wrong here
Adding more capacity typically increases complexity and overhead without addressing the core issue of over-commitment. Lean principles suggest that the problem is not a lack of resources but an excessive amount of active work. Increasing capacity often just masks the inefficiency of having too many concurrent initiatives.
- ✓
Lower the WIP limits for the 'Review' and 'Analysis' states on the Portfolio Kanban.
Why this is correct
Lowering WIP limits is the standard Lean method to expose bottlenecks and force team focus. By restricting the number of epics in progress, the organization is compelled to finish current tasks before pulling new items, which reduces queue lengths, improves cycle time, and ensures that resources are truly focused.
- ✗
Prioritize all incoming Epics using a simple First-In-First-Out (FIFO) queueing system.
Why it's wrong here
FIFO is inefficient in a Lean Portfolio because it ignores the economic value and urgency of different epics. LPM requires prioritizing work based on Weighted Shortest Job First (WSJF) to ensure that the most valuable and time-sensitive tasks are completed first, rather than just the oldest requests.
- ✗
Encourage teams to multitask across different epics to keep all projects moving forward.
Why it's wrong here
Multitasking is a major source of waste in Lean organizations due to context switching costs. Instead of moving all projects slightly, the goal is to complete high-value epics one by one. Encouraging multitasking actually exacerbates the WIP problem and extends total lead times for all portfolio initiatives.
Visual reference
About these practice questions
Courseiva writes every SAFe-Agilist question from scratch — 315 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SAFe-Agilist practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAFe-Agilist exam.