SAFe-Agilist Product Development Flow Practice Question
A SAFe Portfolio is experiencing long lead times for epics due to a large number of epics in the portfolio backlog. The Lean Portfolio Management (LPM) team wants to improve flow by applying the principles of Lean-Agile. Which action is most effective?
⚠ Common exam trap
The trap here is thinking that more epics in the backlog gives teams more choices and thus better outcomes, when it actually creates longer queues and delays.
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 Work in Process (WIP) limit for epics in the portfolio backlog and actively manage the queue.
Limiting WIP at the portfolio level is a direct application of Lean-Agile principles to reduce queue size and lead time. By capping the number of epics in process and managing the queue, the LPM team can improve flow, increase predictability, and deliver value faster. Other options increase WIP or introduce bias, which harm 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.
- ✗
Assign each epic to a dedicated team to avoid context switching.
Why it's wrong here
Creating dedicated teams for each epic increases handoffs and reduces flexibility, often leading to idle capacity and longer lead times. SAFe promotes cross-functional Agile Teams that pull work from a prioritized backlog, which minimizes handoffs and improves flow. Dedicated teams can also create silos and reduce the ART's ability to respond to change.
- ✗
Increase the number of epics in the backlog to give teams more options for selection.
Why it's wrong here
Adding more epics increases the queue length and variability, which leads to longer lead times and less predictability. SAFe advises against large backlogs because they hide priorities and create waste. More options do not improve flow; they overwhelm the system and delay delivery of the most important work.
- ✗
Prioritize epics based on the loudest stakeholder to ensure alignment.
Why it's wrong here
Prioritizing by stakeholder volume rather than economic value or WSJF disrupts flow and can lead to suboptimal decisions. SAFe emphasizes using Weighted Shortest Job First (WSJF) to prioritize based on cost of delay and job size, which optimizes flow and economic outcomes. This approach ignores that principle and introduces bias.
- ✓
Implement a Work in Process (WIP) limit for epics in the portfolio backlog and actively manage the queue.
Why this is correct
Applying a WIP limit to the portfolio epic backlog directly reduces queue size and lead time. SAFe recommends limiting WIP at all levels, including the portfolio, to accelerate flow. By actively managing the queue and only pulling new epics when capacity is available, the LPM team can improve predictability and deliver value faster.
About these practice questions
This SAFe-Agilist question is part of Courseiva's 315-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.