Risk ROAM report: Legacy experience

Note: This article is for the legacy experience of the Risk ROAM report. To enable the new experience, which was released for preview in version 10.131.0, switch on the New experience toggle found in the upper-right corner of the page. To return to the legacy experience, switch off the toggle.  

RiskROAMToggleZoomed.png

If you do not see the new experience toggle, contact your Advisory Services representative or Atlassian Support to have the preview enabled for your environment.

The risk ROAM report shows all risks by the ROAM category with quick view graphics (open vs. closed, risk of occurrence, and impact of occurrence). The ROAM-based risk management model is a method for scaling risk management and implies the following:

  • Resolved. A risk is addressed and is no longer a concern.
  • Owned. Someone takes responsibility for a risk.
  • Accepted. Nothing more can be done. If the risk occurs, the release may be compromised.
  • Mitigated. The team has a plan to adjust if necessary. 

To navigate to this report:

  1. Select Programs in the top navigation bar and select the program you want to view information about.
  2. On the sidebar, select More items in the list of options.
  3. Select Risks; the risks page displays.
  4. On the risks page, select the More Actions button on the toolbar.
  5. Select Risk ROAM Report; the report displays.

OR

  1. Select Programs in the top navigation bar and select the program you want to view information about.
  2. On the sidebar, select Reports in the list of options.
  3. Select Risk ROAM report; the report displays.

Prerequisites

  1. PI must exist in the system and be tied to a program. 
  2. Themes, epics, and features must exist in the system. 
  3. Risks must be created. 

How are report values calculated? 

  • Resolved = the percent (number) of risks marked as Resolved in the selected PI and are no longer a concern.
  • Owned = the percent (number) of risks marked as Owned in the selected PI, which someone took the responsibility for.
  • Accepted = the percent (number) of risks marked as Accepted in the selected PI, due to which the release may be compromised.
  • Mitigated = the percent (number) of risks marked as Mitigated in the selected PI, which the team has a plan for.
  • Open vs Closed = the number (percent) of closed and open risks (as identified on the Risk page).
  • Risk of Occurrence = the chance of a risk occurring (as identified on the Risk page).
  • Impact of Occurrence = the impact a risk may have (as identified on the Risk page).

To change the status of a risk, simply drag and drop it in one of the sections: Resolved, Owned, Accepted, or Mitigated.

 ROAM_Report_111_Draft.png

How to interpret this report

The risk ROAM report provides an easily consumable view of all risks by ROAM category with quick view graphics by key management categories. This report is a visualization of the risks identified by team members and managers who collaborated to decide how to handle them. This report is visible to different team roles, starting with the team members and going up to Scrum Masters, RTEs, Product and Portfolio Managers.

 

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.