1. What
   1. Strategy for Managing Risks by SAFe
2. When and Where
   1. PI planning
   2. PI Execution
   3. System Demos
3. Why
   1. to know more about product and project
   2. to save costs
   3. to be more confident
   4. to forecast possible problems
4. How
   1. During PI planning: teams identify program risks
      1. add risks to the Program Risks area
         1. a risk may be added, and then removed (if the team identifies a mitigation strategy)
   2. During Final Plan Review, all Program Risks are ROAMed one by one. Add additional information about the risk.
      1. Resolved
         1. The teams agree that the risk is no longer a concern
      2. Owned
         1. Someone on the train takes ownership of the risk since it cannot be resolved during PI planning
      3. Accepted
         1. Some risks are just facts or potential problems that must be understood and accepted
      4. Mitigated
         1. Teams identify a plan to reduce the impact of the risk
      5. with honesty and transparency:
         1. use ROAM board
   3. During PI Execution and System Demos, the ROAM Board is periodically reviewed and risks are adjusted
   4. Stages (ISO 14971)
      1. identification
      2. assessment
      3. control
         1. mitigation
         2. acceptance
      4. result
         1. informing about risk management
      5. periodic risk review
5. Who
   1. Dev and Discovery Teams
6. How Many
   1. find the balance