i) Reactive risk strategy
•Reactive risk strategy follows that the risks have to be tackled at the time of their occurrence.
•No precautions are to be taken as per this strategy.
•They are meant for risks with relatively smaller impact.
•More commonly, the software team does nothing about risks until something goes wrong.
•Then, the team flies into action in an attempt to correct the problem rapidly. This is often called a fire-fighting mode.
The reactive risk management is an essential element of:
•Mitigating safety events after hazard has occurred;
•Minimizing damage from critical safety situations;
•Acting quickly and efficient ly in response to undesirable incidents; and
•High quality decision making in react ion to safety data (threats, risk,etc.).
ii)Proactive risk strategy
It follows that the risks have to be identified before start of the project.
They have to be analyzed by assessing their probability of occurrence, their impact after occurrence, and steps to be followed for its precaution.
•They are meant for risks with relatively higher impact. The primary goals of proactive risk management are:
•Identify behaviors that lead to hazard occurrence, and stop it before it happens;
•Identify root causes before they lead to hazard occurrence; and
•Understand safety “inputs” of your program – i.e., underlying causes that lead to safety performance.
0 Comments