ROAM & Risk Management Under SAFe®

April 03, 2015

The importance of managing risks in your software projects need not be further emphasized. Even if you’re not working on safety critical products, risks have the potential to fundamentally derail your projects. With safety critical projects however, it is even more obvious that product (functional) risks mean a serious threat not only to your project’s success, but also to your company’s reputation. At the very least, implementing adequate risk management could help cut your overhead costs.

So one thing is clear: managing risks is imperative in most development projects. That is why several times over the past few years, we have covered topics such as the Benefits of Applying an Appropriate Risk Management Lifecycle on our blog, and we have also addressed the question of risk management in one of our recent webinars.

Considering that more and more companies are transitioning to Agile to deliver complex products, however, risk management is becoming more of an issue. While a single Agile team may successfully cover and mitigate its risks using simple methods, large enterprises that scale Agile using SAFe® face the challenge of also scaling their risk management.

Scaled Risk Management & ROAM

There doesn’t seem to be a silver bullet solution to scaling your risk management across the three levels introduced by Scaled Agile Framework (SAFe®): the Team, Program, and Portfolio levels. However, categorizing your risks helps treat them adequately.

Quite naturally, most practitioners agree that code-level risks are managed at the team level, during Program Increment planning. Higher-level (project or program) risks that could affect the whole Agile Release Train (ART) should be escalated to the Program level. Thus, your teams won’t have to worry about the same risk twice – all risk will be identified, listed and their mitigation planned at the appropriate level. (While there may be certain Portfolio-level risks, managing these should be covered by the organization’s Project Portfolio Management or PPM efforts, the details of which is outside the scope of this article.)

Whichever level you’re looking at, one widely used tool in scaling risk management under SAFe® is the ROAM board. It is used during PI planning to identify and analyze risks and issues. To make sure all the risks are covered, the goal of this technique is to Resolve, Own, Accept (by the product management team) or Mitigate all risks (hence the acronym ROAM).

risk_management_roam ROAM & Risk Management Under SAFe® SAFe

Potential issues that are solved on the Team-level ROAM board don’t get transferred onto the Program-level ROAM board. The mitigation of the identified risks can follow a course similar to that of any Agile project. The main benefit of using a ROAM board is that it helps ensure that all the risks are covered – after a ROAM session, you should get commitment to resolve all the identified issues one way or the other. Another benefit is that ROAMing can be simply moved to a collaborative online tool, facilitating cooperation between geographically distributed teams.

Collaborative Risk Management

Collaboration is key in risk management: identifying potential risks is supported by the cumulative experience of your team members, and having your risks in a single tool helps ensure total risk coverage. Using a tool that simultaneously supports implementing SAFe® across your organization and scaling your risk management efforts provides an advantage. What’s more, it could help ensure complete traceability of risks & ensure their coverage.

codeBeamer is not only the first proven implementation of SAFe®, it also comes with advanced risk management functionality. The Kanban board in codeBeamer is a flexibly customizable tool that you can easily use to conduct ROAM sessions. Risk trackers help you ensure complete traceability and risk coverage – after ROAMing your risks, you can simply assign mitigation tasks and trace these through to testing & release.

Risk Matrix Diagrams support your risk mitigation efforts and ROAM, facilitating the acceptance of risks below a certain tolerable level by visualizing your risks. Thus, using a SAFe®-ready ALM to manage all your development processes helps you scale risk management, while offering all the benefits associated with using a single-repository, end-to-end ALM solution.

Interested in finding out more about SAFe®? Sign up for our free webinar on 29 April titled SAFe: Scaled Agile Framework in Practice!

SAFe® and Scaled Agile Framework are registered trademarks of Scaled Agile Inc.

facebook ROAM & Risk Management Under SAFe® SAFe twitter ROAM & Risk Management Under SAFe® SAFe google ROAM & Risk Management Under SAFe® SAFe linkedin ROAM & Risk Management Under SAFe® SAFe



Related E-Book

SAFe® Template Brochure

First Name

Last Name

Email Address


Phone Number


Kristof Horvath

Written by

Kristof holds a BA in Commerce and Marketing and is especially passionate about inbound and content marketing. On the Intland blog, he is covering topics related to application lifecycle management and agile methods.

Kristof Horvath has written 103 posts for Intland Software.

4 Comments. Leave new

sandeep mishra
3 April 2015 16:26

Well written , nicely explained article

sandeep mishra
3 April 2015 16:26

Well written , nicely explained article , Thanks a lot


Thanks Sandeep, glad you liked it. Please feel free to share your insights / ideas / best practices, if you have any.

SAFe Invitations – Part 2/3 – Management Workshop and Vote-of-confidence-driven open space in QuickStart | Yuval Yeret on Lean/Agile/Flow
3 November 2015 19:01

[…] haven’t tried it yet but asking people to ROAM (Resolve/Own/Accept/Mitigate) each risk/issue like we do in PI Planning seems like a great […]


Leave a Reply

Your email address will not be published. Required fields are marked *