Risk Management & Mitigation Flashcards

In Jira, a team wants to track risks visually throughout a sprint. Which approach best supports ongoing risk visibility?

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.

A risk has been identified with a high probability but very low impact. What is the recommended agile risk response strategy?

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.

Which Jira field configuration best helps teams distinguish between a blocked issue caused by an external dependency risk versus an internal team impediment?

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.

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?

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.

In a risk register maintained in Confluence, what does 'risk owner' specifically mean?

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.

A team using SAFe with Jira Align wants to surface risks that span multiple Agile Release Trains. Which feature should they use?

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.

Which metric in Jira best indicates that a team's risk mitigation efforts are reducing technical debt risk over successive sprints?

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.