Reactive risk strategies • 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. • Proactive risk strategies • It follows that the risks have to be identified before start of the project. • They have to be analysed by assessing their probability of occurrence, their impact after occurrence, and steps to be followed for its precaution.