A. Resolved, Owned, Approved, Mitgated
B. Owned, Mitigated, Active, Resolved
C. Resolved, Assigned, Mitigated, Owned
D. Owned, Mitigated, Resolved, Accepted
The Correct Answer is
D. Owned, Mitigated, Resolved, Accepted
Explanation
ROAM is an acronym used to classify program risks in the Scaled Agile Framework (SAFe). It stands for:
- Resolved: Risks that have been eliminated or addressed before or during the PI Planning.
- Owned: Risks that have been identified and have an owner assigned to them, but have not yet been resolved. The owner is responsible for managing and resolving the risk.
- Accepted: Risks that cannot be resolved or mitigated in the current context and must be acknowledged and accepted as part of the program’s constraints or conditions.
- Mitigated: Risks that have actions planned or taken to reduce their impact or likelihood, thus minimizing the risk’s effect on the program.
Therefore, ROAM represents Resolved, Owned, Accepted, and Mitigated.
The ROAM technique for risk management is a critical component of the Scaled Agile Framework (SAFe), particularly during Program Increment (PI) Planning. It provides a structured approach for identifying, classifying, and addressing risks, ensuring that they are managed proactively. Let’s delve deeper into each aspect of ROAM and its significance in the context of Agile and SAFe:
Resolved (R)
- Definition: Resolved risks are those that have already been dealt with by the time of the PI Planning or during the PI Planning event itself. These risks are no longer considered threats to the program’s objectives.
- Importance: Highlighting resolved risks during PI Planning serves multiple purposes. It provides reassurance to the team and stakeholders, demonstrates proactive risk management, and shares lessons learned that can be applied to future risk mitigation efforts.
Owned (O)
- Definition: Owned risks are those that have been identified and assigned to a specific individual or team who is responsible for managing them. Ownership implies responsibility for monitoring the risk and implementing mitigation strategies as needed.
- Importance: Assigning ownership ensures that there is clear accountability for addressing each risk. It prevents risks from being overlooked and ensures that someone is always thinking about how to reduce the likelihood and impact of the risk.
Accepted (A)
- Definition: Accepted risks are those that, after careful consideration, are deemed unavoidable or not cost-effective to mitigate. These risks are consciously acknowledged and accepted by the team and stakeholders.
- Importance: Accepting a risk involves understanding its potential impact and preparing to deal with the consequences. This decision is strategic, recognizing that resources are limited and not all risks can (or should) be mitigated. Acceptance is a form of risk management and requires continuous monitoring in case the risk’s severity changes.
Mitigated (M)
- Definition: Mitigated risks are those for which specific actions have been planned or implemented to reduce their likelihood or impact. Mitigation strategies are designed to lessen the potential negative effects of a risk on the program.
- Importance: Mitigation is a proactive step in risk management. By identifying and implementing measures to reduce the severity of risks, the program can continue to move forward with a reduced level of threat. Effective mitigation requires continuous assessment to ensure the strategies are working as intended.
Application in SAFe
- During PI Planning: ROAM is used as a live activity where teams and stakeholders collaborate to identify and assess risks. By the end of the PI Planning event, each identified risk should be categorized into one of the ROAM categories.
- Continual Process: Risk management using ROAM is not a one-time activity. As the PI progresses, risks should be reevaluated, and their status updated based on new information or changing conditions.
Conclusion
The ROAM classification system facilitates a dynamic and collaborative approach to risk management within the SAFe framework. By categorizing risks as Resolved, Owned, Accepted, or Mitigated, teams can ensure that risks are systematically identified, analyzed, and addressed. This process helps in maintaining a clear focus on delivering value while managing the uncertainties inherent in complex development environments. ROAM not only aids in risk management but also fosters a culture of openness and continuous improvement.