Risk avoidance is designed to avoid any identified risks to the project. Within an IS development project,
this may include avoiding the use of an untested technology or avoiding changes to the scope of the
system.
Risk transference involves the transfer of risk to another party. Risk transference is often facilitated
through the use of contracts in which the risk associated with a given activity is transferred to another
party. Depending on the type of contract being used, risk may be transferred from the seller to the buyer
or from the buyer to the seller.
Risk mitigation is used to reduce, eliminate, or transfer the chances of risk occurrence or to reduce the
impact of the risk on project objectives. An example of risk mitigation during an IS development project is
the use of a known technology provider rather than reliance on a less established vendor.
Risk acceptance occurs when managers simply decide that an effective response cannot be developed for
a specific risk. In this case, a decision is made to accept that a given risk may occur and either to do
nothing (passive response) or to plan alternative strategies (active response) should the risk occur. For
example, an active response during an IS development project may mean accepting that a new version of
a particular software may not function as intended and developing an alternative plan to use a previous
version of the software.