RISK-Roaming

Risks are discussed in the TIPE by using the RISK roaming method. Risks can affect the progress of the TI.
Risk roaming falls on all participants in the TIPE such as members of the scalable Agile Units, stakeholders, business owner(s), and individuals in the C suit.

ROAM allows the management of risks. These are the four categories into which the risks can be grouped:

  1. Resolved: The risk is not a problem or obstacle (anymore).
  2. Owned: A member of the team takes responsibility (ownership) for the risk because it could not be solved in the meeting.
  3. Accepted: The risk can’t be solved, so it must be understood and accepted as it is.
  4. Mitigated: A course of action has been determined to reduce the likelihood of the risk occurring by taking appropriate action.

After the RISK roaming, risks that need to be followed up during the TI are moved to the Program Risk Board so that they can be tracked.

Risks are transparently managed with the RISK roaming method. Smaller risks are addressed at the team level, while larger risks are resolved at the transformation program level with the Transformation Master and Transformation Owner. The TM is responsible for tracking the risks together with the TO.

ROAM can be used to identify all risks that may affect a project.

Share this post