ACP Risk Management & Mitigation 2 — Questions and Answers
Question 1: In Jira, a team wants to track risks visually throughout a sprint. Which approach best supports ongoing risk visibility?
- Create a dedicated risk epic with linked stories for each identified risk
- Add a custom 'Risk' issue type and display it on the sprint board with a distinct color label (Correct answer)
- Log risks only in the retrospective notes after each sprint
- Store all risks in a shared Confluence table updated weekly
Correct answer: Add a custom 'Risk' issue type and display it on the sprint board with a distinct color label
A custom Risk issue type visible on the sprint board gives the team continuous, real-time visibility into risk status without switching tools.
Question 2: A risk has been identified with a high probability but very low impact. What is the recommended agile risk response strategy?
- Escalate immediately to the program manager
- Accept the risk and monitor it with a low-priority flag (Correct answer)
- Mitigate it with the same urgency as a high-impact risk
- Transfer the risk to an external vendor
Correct answer: Accept the risk and monitor it with a low-priority flag
Risks that are highly probable but low-impact are typically accepted and monitored rather than consuming significant mitigation resources.
Question 3: Which Jira field configuration best helps teams distinguish between a blocked issue caused by an external dependency risk versus an internal team impediment?
- Using different assignees for blocked issues
- Creating separate 'Blocked - External Risk' and 'Blocked - Internal' labels or statuses (Correct answer)
- Moving all blocked issues to a dedicated Blocked sprint
- Flagging all blocked issues identically and sorting by reporter
Correct answer: Creating separate 'Blocked - External Risk' and 'Blocked - Internal' labels or statuses
Distinct labels or statuses for external versus internal blockages allow teams and stakeholders to route escalation appropriately and measure risk sources.
Question 4: A Scrum team discovers mid-sprint that a critical third-party API they depend on will be deprecated next month. What is the FIRST action according to agile risk principles?
- Continue the sprint and address it during the next planning session
- Immediately identify and evaluate alternative API options and add a risk story to the backlog (Correct answer)
- Cancel the sprint and restart with a risk-focused sprint goal
- Raise a change request to the project sponsor
Correct answer: Immediately identify and evaluate alternative API options and add a risk story to the backlog
Agile risk management calls for immediate identification, evaluation of options, and backlog capture so the team can plan a timely response without disrupting flow unnecessarily.
Question 5: In a risk register maintained in Confluence, what does 'risk owner' specifically mean?
- The person who first reported the risk
- The stakeholder responsible for funding risk mitigation
- The individual accountable for monitoring and executing the agreed response to a risk (Correct answer)
- The project manager who approves all risk entries
Correct answer: The individual accountable for monitoring and executing the agreed response to a risk
The risk owner is the person accountable for monitoring the risk and ensuring the mitigation or contingency plan is executed as agreed.
Question 6: A team using SAFe with Jira Align wants to surface risks that span multiple Agile Release Trains. Which feature should they use?
- Jira sprint reports filtered by team
- ROAM board at the Program Increment level in Jira Align (Correct answer)
- Confluence meeting notes from ART sync
- Jira dashboard gadget filtered by epic
Correct answer: ROAM board at the Program Increment level in Jira Align
The ROAM board (Resolved, Owned, Accepted, Mitigated) in Jira Align is specifically designed to manage cross-ART program-level risks during PI Planning.
Question 7: Which metric in Jira best indicates that a team's risk mitigation efforts are reducing technical debt risk over successive sprints?
- Decreasing number of flagged issues sprint over sprint (Correct answer)
- Increasing story point velocity
- Higher number of issues moved to Done each sprint
- Reduction in the number of unresolved bugs older than 30 days
Correct answer: Decreasing number of flagged issues sprint over sprint
A consistent decrease in flagged (blocked or at-risk) issues over time signals that the team's mitigation actions are effectively reducing risks before they become blockers.
ACP Risk Management & Mitigation 2
In Jira, a team wants to track risks visually throughout a sprint.
Which approach best supports ongoing risk visibility?