What an interesting Topic to start with, and for sure happened many times due to unexpected cultural events that reprioritized the work. Many examples I have encountered were due to stakeholder alignment.

Hello Marium, 
I would not share a dedicated method for risk management however if relevant using ROAM can ultimately help you if risks arise late in the project frequently.

ROAM is an acronym representing four ways to handle risks:

• Resolved: The risk has been effectively eliminated or verified as non-threatening. No further action is required, and the risk can be closed in risk registers.
• Owned: A specific individual or team is assigned responsibility for managing the risk. This status indicates that the risk still requires active handling, monitoring, and follow-up.
• Accepted: The risk cannot be resolved or mitigated and is acknowledged as an acceptable part of the project. Teams plan to manage its impact if it occurs.
• Mitigated: A plan is in place to reduce the likelihood or impact of the risk. Action steps are defined to minimize potential negative effects .

Implementation in Agile and SAFe

ROAM is commonly applied during PI Planning, a key SAFe event where teams align…

Read more