SAFe-Agilist Product Development Flow Practice Question
A Release Train Engineer (RTE) notices that the ART's flow is frequently disrupted by late-breaking dependencies that are discovered during the iteration. Which SAFe practice best addresses this issue during PI Planning?
⚠ Common exam trap
The trap here is thinking that more frequent demos or dedicated integrators can replace the need for proactive dependency mapping during PI Planning.
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
✓
Conduct a formal dependency mapping session where teams identify and visualize cross-team dependencies on the ART board.
Formal dependency mapping during PI Planning allows teams to identify and visualize cross-team dependencies early, enabling proactive sequencing and adjustment. This SAFe practice reduces late-breaking surprises and helps maintain flow. Other options are either reactive or do not systematically address the root cause.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Allow teams to work independently and resolve dependencies as they arise during the iteration.
Why it's wrong here
This reactive approach leads to delays, firefighting, and unpredictable flow. SAFe promotes proactive dependency management during PI Planning to avoid mid-iteration surprises. Letting dependencies surface during the iteration increases WIP and wait times, harming overall ART flow and predictability.
- ✗
Increase the number of system demos to catch integration issues earlier.
Why it's wrong here
System demos are valuable for feedback and integration, but they occur at the end of iterations and do not prevent late-breaking dependencies discovered during the iteration. The issue is about proactive identification during planning, not later detection. More demos alone will not resolve the underlying planning gap.
- ✗
Assign a dedicated integrator to each team to handle all external dependencies.
Why it's wrong here
While integrators can help, assigning one per team does not systematically surface dependencies across the ART and can create bottlenecks. SAFe emphasizes collective ownership and visualization of dependencies during PI Planning. This approach may reduce some friction but does not address the root cause of late discovery.
- ✓
Conduct a formal dependency mapping session where teams identify and visualize cross-team dependencies on the ART board.
Why this is correct
Dependency mapping during PI Planning is a core SAFe practice that helps teams surface and visualize cross-team dependencies early. By identifying dependencies before the PI begins, teams can adjust plans, sequence work, and reduce the likelihood of late-breaking issues that disrupt flow. This proactive approach is essential for maintaining smooth delivery.
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.