This mode is similar to the fire fighting mode, which is characterized by allowing software risks to occur until software risks bring trouble to software project development. For example, in view of the risk that Xiao Liu left the software project team, the person in charge of the software project knew the software risk, but did not take any measures. One month after Xiao Liu left the project team, other members of the software project team needed to integrate and test the subsystem module that Xiao Liu was responsible for, only to find that the relevant code had not been written yet. Obviously, this risk has seriously affected the work of other people in the software project team at this time, which will make the progress of the software project lag behind. In this case, the person in charge of the software project takes corresponding measures to deal with the risks (such as transferring other personnel to take over Xiao Liu's work).

Fault handling

In this model, both the project team members and the person in charge know the potential risks, but allow the occurrence and evolution of software risks, and only take countermeasures after the risks occur. For example, in view of the risk that Xiao Liu will leave the project team, the project team did not take any measures. The day after Xiao Liu left the project team, the project team decided to transfer other personnel to take over Xiao Liu's work, but at this time it was no longer possible to hand over the project with Xiao Liu face to face.

Obviously, both crisis management mode and failure handling mode are very negative in dealing with risks, so they are not recommended in the implementation of software projects.

Risk mitigation

In the risk mitigation mode, project team members and leaders consciously identify various software risks in the process of software development, and make remedial measures for these software risks in advance, but do not take any preventive measures. That is to say, the members of the project team and the person in charge identify and analyze in advance which adverse events may occur, wait for them to happen, and formulate countermeasures after these events occur. For example, the members of the project team and the person in charge already knew that Xiao Liu was leaving the project team, but they did not take any measures to prevent this incident from happening and let it develop. However, they have taken corresponding measures. Xiao Liu Yi left the project team, and Xiao Zhang took over Xiao Liu's job. Obviously, compared with crisis management and failure management mode, risk mitigation mode has become more active in dealing with and responding to software risks.

risk prevention

Risk prevention mode plans and executes risk identification and risk prevention as a part of software projects. Project team members and responsible persons identify and analyze in advance which adverse events may occur, formulate countermeasures when they occur, and take measures to prevent them from happening. For example, the members of the project team and the person in charge know that Xiao Liu is leaving the project team. On the one hand, they discussed with Xiao Liu whether they could wait until the project was completed, on the other hand, they formulated corresponding measures. Once Xiao Liu leaves the project team, Xiao Zhang will take over from Xiao Liu.

Eliminate the root cause

In this mode, project team members and leaders should not only identify all kinds of potential software risks in the process of software development, but also analyze the main factors leading to these software risks and take active measures to eliminate the root causes of software risks. In other words, the project team members and the person in charge identify in advance which adverse events may occur, formulate countermeasures when they occur, and take measures to eliminate the root causes of software risks and put an end to the occurrence of software risks. For example, in view of the risk of Xiao Liu leaving the project team, the project team members and the person in charge have formulated corresponding measures. Once Xiao Liu leaves the project team, Xiao Zhang will take over Xiao Liu's job. At the same time, through communication with Xiao Liu, it is found that the main reason why Xiao Liu left the project team is that Xiao Liu thinks that the salary given by the company is too low, which does not match his technical level and contribution to the company and the software project team. In view of this factor, the company and the software project team consider increasing Xiao Liu's salary and subsidy to discourage Xiao Liu from leaving the software project team.

Obviously, the latter three risk management modes are more active in dealing with software risks and can effectively reduce the negative impact of software risks on software project implementation, so they should be advocated in software project management.