SAFe-Agilist Exploring Lean Portfolio Management Practice Question
A Portfolio Manager is reviewing the Portfolio Kanban to optimize flow. They notice a bottleneck at the 'Review' stage where items wait for long periods before approval. What is the primary Lean Portfolio Management (LPM) action to address this?
⚠ Common exam trap
Many candidates suggest 'adding more resources' or 'increasing the team size' to resolve bottlenecks. This ignores the fundamental Lean principle of managing flow through WIP limits to expose and address constraints.
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
✓
Implement a strict WIP limit for the 'Review' stage.
Improving flow in the Portfolio Kanban requires identifying and addressing constraints. By limiting Work in Process (WIP) at the 'Review' stage, the portfolio team forces prioritization, ensuring that only the highest-value items are processed. This focus prevents context switching and backlog bloating, which are critical for maintaining agility at scale. Effective flow ensures that strategic themes are realized efficiently through the continuous delivery pipeline.
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 Review board to process more items.
Why it's wrong here
Increasing capacity often masks underlying inefficiencies rather than solving them. Simply adding more resources to a bottleneck stage usually results in larger backlogs downstream, failing to address the fundamental need for prioritization and lean flow management within the Portfolio Kanban system.
- ✓
Implement a strict WIP limit for the 'Review' stage.
Why this is correct
WIP limits are the primary mechanism for controlling flow and exposing bottlenecks in a Kanban system. By restricting the number of items in the 'Review' state, the team is forced to resolve existing items before taking on new work, directly reducing wait times and improving throughput.
- ✗
Escalate all pending items to the Portfolio Steering Committee for immediate resolution.
Why it's wrong here
Escalation frequently creates secondary bottlenecks and shifts decision-making away from the decentralized teams intended to manage the flow. This reactive approach ignores the systemic issues causing the delay and undermines the autonomy of the Agile Release Trains to manage their local work effectively.
- ✗
Remove the 'Review' stage entirely to accelerate the flow of Epics.
Why it's wrong here
Removing a stage without analyzing its purpose risks bypassing critical governance and economic evaluation steps. The Review stage exists to ensure alignment with strategic themes and economic feasibility; eliminating it would likely lead to poor investment decisions that do not support portfolio business objectives.
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.