POPM Leadership for PI Planning Practice Question
Exhibit
RISK_LOG: [ { 'RISK': 'Dependency on legacy vendor', 'LEVEL': 'High' }, { 'RISK': 'Lack of test environment', 'LEVEL': 'Medium' }, { 'RISK': 'Team turnover', 'LEVEL': 'High' } ]; ROAM_STATUS: { 'RESOLVED': 0, 'OWNED': 0, 'ACCEPTED': 0, 'MITIGATED': 0 };Refer to the exhibit. The ROAMing session has not yet been conducted. What is the leader's next step?
⚠ Common exam trap
Candidates frequently choose to 'delegate' risk management to individual teams. This misses the point of the ROAMing session, which is to address program-level risks that affect the entire Agile Release Train.
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
✓
Lead the ROAMing session to ensure every identified risk is categorized and owned.
The ROAMing session is mandatory for addressing risks identified during PI Planning. By using the ROAM technique—Resolved, Owned, Accepted, Mitigated—leadership ensures that every risk is accounted for and assigned an action or owner. Leaving risks unaddressed means they are ignored, which is a major danger. Leadership must drive this session to categorize each risk so that teams know exactly how to manage potential threats to their PI objectives.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Have the teams document the risks in their own backlogs and resolve them individually.
Why it's wrong here
Risk management is a shared responsibility that requires transparency across the train. If teams handle risks individually, there is no shared understanding or program-level visibility, and many risks, like external dependencies, cannot be managed by a single team. This would lead to predictable project failures.
- ✓
Lead the ROAMing session to ensure every identified risk is categorized and owned.
Why this is correct
The leader must guide the ROAMing process to ensure all risks are assigned a category and a clear owner. This ensures that everyone knows who is responsible for managing which risk, which is essential for maintaining accountability and reducing the probability of these risks impacting the PI objectives.
- ✗
Ignore the risks as they are just possibilities and not actual work items.
Why it's wrong here
Ignoring risks is the most common cause of PI failure. Risks are not just possibilities; they are threats to the plan. By failing to categorize them, the train misses the opportunity to mitigate them, which almost guarantees that they will become major issues during the Program Increment.
- ✗
Assign all risks to the Product Manager to handle during the next sprint.
Why it's wrong here
The Product Manager cannot resolve all risks alone, especially those related to technical environments or vendor dependencies. Risk management requires input and action from various roles, including Scrum Masters, Architects, and leaders. Concentrating all risk ownership on one person creates a bottleneck and prevents effective resolution.
Visual reference
About these practice questions
One of 336 original POPM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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 POPM 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 POPM exam.