Risk management strategy

From apppm
(Difference between revisions)
Jump to: navigation, search
 
(72 intermediate revisions by one user not shown)
Line 1: Line 1:
−
“When trouble is sensed well in advance in can be easily remedied; if you wait for it to show itself any medicine will be too late because the disease will have become incurable. As the doctors say of a wasting disease, to start with it is easy to cure but difficult to diagnose; after time… it becomes easy to diagnose but difficult to cure.” (Machiavelli, 1514)
+
''Developed by Matthias Koch''
 +
 
 +
 
 +
[[File:ISO 31000-2009 risk management strategy.JPG|thumb|300px|Risk management strategy as defined be ISO 31000:2009<ref>[ISO 31000:2009]</ref>]]
 +
“When trouble is sensed well in advance in can be easily remedied; if you wait for it to show itself any medicine will be too late because the disease will have become incurable. As the doctors say of a wasting disease, to start with it is easy to cure but difficult to diagnose; after time… it becomes easy to diagnose but difficult to cure.” (Machiavelli, 1514) <ref>[Niccolo Machiavelli “The Prince”]</ref>
  
 
When dealing with a project, uncertainties are to be expected, whether the project is influenced by external or internal factors. If an unexpected event turns out to be harmful to the project it is in general terms considered to be a risk.   
 
When dealing with a project, uncertainties are to be expected, whether the project is influenced by external or internal factors. If an unexpected event turns out to be harmful to the project it is in general terms considered to be a risk.   
−
A risk can be defined as the product of the probability of the risk and the impact of the risk. Should a problem be very likely to happen, but have a little or no impact on the project there is little reason in prioritizing the mitigation of the problem.  
+
A risk can be defined as the product of the probability of the risk and the impact of the risk. Should a problem be very likely to happen, but have little or no impact on the project there is little reason in prioritizing the mitigation of the problem. For a problem having a high impact, but very low probability the need to mitigate this problem is likewise not a priority. Should a problem be moderately likely and serious, then the problem is a risk and should be handled.
−
For a problem having a high impact, but very low probability the need to mitigate this problem is likewise not a priority. The impact of a risk is however more severe than the probability. For instance are smaller injuries, which happen often, easier to accept than heavier injuries, which happen more seldom.  
+
The impact of a risk is however more severe than the probability. For instance are smaller impacts, which happen often, easier to accept than heavier impacts, which happen more seldom.  
 
The probability of a problem should however not be neglected. A common way to illustrated this is by playing a small game:
 
The probability of a problem should however not be neglected. A common way to illustrated this is by playing a small game:
  
 
In the construction business many factors must by in order for the project to move forward. Six people are given a dice and a problem. Whenever a person rolls a 1 a problem has occurred which delays the project. Thus the probability of a problem happening is 1/6. The probability of no problem happening is:
 
In the construction business many factors must by in order for the project to move forward. Six people are given a dice and a problem. Whenever a person rolls a 1 a problem has occurred which delays the project. Thus the probability of a problem happening is 1/6. The probability of no problem happening is:
  
−
5/6*5/6*5/6*5/6*5/6*5/6=(5/6)^6=0,33
+
<math>5/6*5/6*5/6*5/6*5/6*5/6=(5/6)^6=0,33</math>
  
 
This means that only a third of the time, the project will progress.
 
This means that only a third of the time, the project will progress.
  
−
If there is no certain way to determine a risk’s impact or probability or multiple risks are compared without having similar impact type (e.g. comparing human casualties against monetary loss) a qualitative approach can be used, where the risk is rated from e.g. 1-5. In this way a prioritized list of risks can be produced. With this list it is possible to determine which risk to take care of first.
+
A useful risk management strategy comprises of the following steps:
 +
*'''Identify''' - Potential risks are identified.
 +
*'''Analyze''' - Identified risks are rated, related to probability and impact.
 +
*'''Assess''' - Analyzed risks are ranked and compared to each other to determine which risk to handle first.
 +
*'''Process''' - Solutions are found to counter effect the risks.
 +
*'''Monitor''' - During the project lifetime, identified risks are monitored and new, potential risks are identified.
  
−
This article will examine ways to identify potential risks, rate their associated probabilities and impacts and process the new knowledge.
+
This article will examine ways to do a successful risk management.
  
−
'''NOTE: This article might be similar to other articles; Risk management + Risk analysis + risk register + Risk management in project portfolios'''
+
To get a better understanding of the different methods provided in this article, an example has been constructed to show how these are used.
 +
The background for the examples are:
 +
 
 +
 
 +
'''Example'''
 +
 
 +
Three friends; Adam, John and Fred, wants to start a business together. Their goal is to sell high-quality fruit, pastry and beverage from specially made bicycles in the downtown area.
 +
They already have contacts with some suppliers and have already purchased the bikes and other equipment for their trade.
 +
During the winter, Fred's cousin, Steve, took a course in risk management and has now offered to help the three friends with their business.
 +
This happens in the start of February and the business will launch medio April.
 +
 
 +
 
 +
== Definitions ==
 +
 
 +
===Risk===
 +
PMBOK defines a risk as:
 +
"An uncertain event or condition that, if it occurs has a positive or negative impact on one or more project objectives such as scope, schedule, cost and quality" <ref>["A Guide to the Project Management Body of Knowledge ( PMBOK® Guide )—Fifth Edition"]</ref>.
 +
 
 +
Put mathematically:
 +
<math>Risk=Impact*probability</math>
 +
 
 +
===Probability===
 +
The probability of a risk is the estimated likelihood of a certain event happening.
 +
 
 +
===Impact===
 +
The impact is the consequences a risk may have on a project. The impact can include: Personal injury, monetary loss, delays, ect.
  
 
== Risk identification ==
 
== Risk identification ==
−
How is a potential risk identified? Which methods to use for identification.
+
 
 +
During the risk identification, a project is scrutinized for potential risks. During the scrutinisation experience is a good asset when determining the potential risks, but other methods do however exists.
 +
Risk identification is the simplest of the risk management steps, since it only requires the project group to think of possible threads and opportunities. Risk identification is however the most important step and should be repeated iterativly during the project lifetime to ensure the safety of the project.
 +
 
 +
=== Identification methods ===
 +
 
 +
Instead of relying on experience and common sense, when determining the possible risks, taxonomy-facilitated brainstorming <ref>[NASA "NASA Risk management handbook"]</ref> could be used.
 +
Brainstorming techniques includes:
 +
* Check-lists
 +
* [[What-if analysis]]
 +
* [[Failure mode and effect analysis]] (FMEA)
 +
* [[Hazard and operability studies]] (HAZOP)
 +
These exercises should help the brainstorming and thought processes to identify risks.
 +
 
 +
Another method<ref>[Department of Defense "Risk management guide for DOD acquisition]</ref> is to ask "What could go wrong?", and answer it when relating to the following subjects:
 +
* Current and proposed staffing, design, process, resources, suppliers, dependencies, operational employment, ect.
 +
* Monitoring test results
 +
* Reviewing shortfalls against expectations
 +
* Analyzing negative trends
 +
 
 +
 
 +
=== Example ===
 +
 
 +
Steve arranges a meeting with the three friend, to discuss possible risks. The group comes up with a lot of possible risks, by telling Steve about their business model and answering his ".. but what if.."-questions. Some of these are listed below:
 +
 
 +
1. Bicycles are unusable due to wear, damage or theft. This would induce a serious impact on the business since they only have three bicycles and relies on mobility.
 +
 
 +
2. The remaining suppliers does not sign a contract. Products will either not be available, leading to poorer service or more expensive deals will have to be struck to ensure the right products.
 +
 
 +
3. Traffic accidents leading to sick days. Since the business revolves around bicycling in a busy city.
 +
 
 +
4. Suppliers cannot meet demand. The decision to use high quality good, means that changes to increase supply quantities takes a long time to realize.
 +
 
 +
5. Sickness or injuries. The business relies on that Adam, John and Fred are able to bike in any weather. Should any one of them be unable to work due to sickness or injuries the business will lose a third of it earnings.
 +
 
 
== Risk analysis ==
 
== Risk analysis ==
−
Methods for analyzing risks for further processing.
+
With the risks identified it is now possible to do a risk analysis. This analysis determines each risk's probability and impact.
 +
 
 +
===Probability rating===
 +
I can be very tricky to determine the exact probability of a given risk and knowing the probability might increase the complexity of the following risk assessment.
 +
A standardized way to rate probability is by using the table below<ref>[Department of Defense "Risk management guide for DOD acquisition]</ref>. Whether the rating is based on experience, common sense or actual facts does not matter at this step.
 +
 
 +
{| class="wikitable collapsible"
 +
! style="background:#d0e5f5" | Probability level
 +
! style="background:#d0e5f5" | Likelihood
 +
! style="background:#d0e5f5" | Probability
 +
|-valign="top"
 +
| 1 || Not likely || ~10%
 +
|-
 +
| 2 || Low likelyhood || ~30%
 +
|-
 +
| 3 || Likely || ~50%
 +
|-
 +
| 4 || Highly likely || ~70%
 +
|-
 +
| 5 || Near certainty || ~90%
 +
|-
 +
|}
 +
 
 +
Note that a probability of 0% is not possible, since that would mean that the event '''will not''' happen.
 +
 
 +
Likewise is a probability of 100% neither possible, since that would mean that the event '''will''' happen.
 +
 
 +
===Impact rating===
 +
Like determining the level of probability of a risk, the level of impact is equally as tricky to determine. There for a rating scale has been presented below<ref>[Department of Defense "Risk management guide for DOD acquisition]</ref>.
 +
The difference between impact rating and probability rating is that, the impact rating tries to embrace consequences regarding human health, expenses and delays and compare these different subjects. Therefore is a standardized method of determining level of impact useful.
 +
Like probability the rating can be based on experience, common sense or actual numbers.
 +
 
 +
{| class="wikitable collapsible"
 +
! style="background:#d0e5f5" | Impact level
 +
! style="background:#d0e5f5" | Technical performance
 +
! style="background:#d0e5f5" | Schedule
 +
! style="background:#d0e5f5" | Cost
 +
|-valign="top"
 +
| 1 || Minimal or no consequence to performance || Minimal or no impact || Minimal or no impact
 +
|-
 +
| 2 || Minor reduction in performance or supportability  || Able to meet key dates || Budget or unit production cost increases. '''<1% of budget'''
 +
|-
 +
| 3 || Moderate reduction in performance or supportability with limited impact in objectives.|| Minor schedule slip. Able to meet key milestones with no schedule float. || Budget or unit production cost increases. '''<5% of budget'''
 +
|-
 +
| 4 || Significant degradation in performance or major shortfall in supportability. May jeopardize success. || Critical path affected ||Budget or unit production cost increases. '''<10% of budget'''
 +
|-
 +
| 5 || Severe degradation in performance. Will jeopardize success || Cannot meet key milestones ||Exceeds threshold '''>10% of budget'''
 +
|-
 +
|}
 +
 
 +
===Uncertainty rating===
 +
When the probability and impact is determined for a risk, the risk can be assessed. However it would be wise to consider the uncertainty of the analysis. This can be done by using the table below<ref>[NASA "NASA Risk management handbook"]</ref>.
 +
 
 +
{| class="wikitable collapsible"
 +
! style="background:#d0e5f5" | Uncertainty factor
 +
! style="background:#d0e5f5" | Associated question to be answered
 +
|-valign="top"
 +
| Uniqueness || Is this risk issue unique or new compared to risks that have occurred in other  projects?
 +
|-
 +
| Cross-cutting Character || Does this risk issue affect a large number of functions, hardware elements, software elements, or procedures and/or have the potential to cross organizational lines?
 +
|-
 +
| Complexity || Does this risk issue involve complex interactions between or among hardware elements, software elements, organizations, and/or individuals?
 +
|-
 +
| Propagation Potential || Could this risk issue lead to a propagation of events that could result in more severe consequences than the immediate events caused by the risk?
 +
|-
 +
| Detectability || Is there anything that inhibits the ability to detect the full extent of the risk and track its progress?
 +
|}
 +
 
 +
If a "Yes" is the answer to any of the above mentioned questions, then the risk faces certain uncertainties. These uncertainties should be rated in a manner fitting to group doing the risk analysis.
 +
An example might be:
 +
*The risk's uncertainty is marked Red if two or more questions have gotten a "Yes".
 +
*The risk's uncertainty is marked Yellow if one question has gotten a "Yes".
 +
*The risk's uncertainty is marked Green
 +
 
 +
 
 +
=== Example ===
 +
 
 +
Following the example, Steve talks to the three friends about how likely they feel each risk is and what impact it could have.
 +
All this, Steve puts into a matrix.
 +
 
 +
{| class="wikitable collapsible"
 +
! style="background:#d0e5f5" | Risk number
 +
! style="background:#d0e5f5" | Probability
 +
! style="background:#d0e5f5" | Impact
 +
|-valign="top"
 +
| 1 - Lack of bikes || The guys think that this might happen to some times during a season. || The bikes are easily replaced or repaired, but this is a bit expensive.
 +
|-
 +
| 2 - Missing suppliers || The guys believe that all contracts are sign before start-up, this is not likely. || This could prove to be a moderate set back.
 +
|-
 +
| 3 - Accidents || The friends believe that this is not likely to happen, since they are all experienced cyclists || This will have a serious impact.
 +
|-
 +
| 4 - Lacking supplies || Adam, John and Fred does not think is likely to happen || However, should the business be out of stock it could take weeks to resupply, which will be a great loss of money.
 +
|-
 +
| 5 - Sickness or injury || It is believed that this is very likely to happen, since non of them are used to biking or being outside for 8 hours. || Serious illnesses and traffic accidents aside, this will only have a small impact since it is most likely to only infer a single sick day or two.
 +
|}
 +
 
 +
Steve determines the risk levels:
 +
 
 +
{| class="wikitable collapsible"
 +
! style="background:#d0e5f5" | Risk number
 +
! style="background:#d0e5f5" | Probability
 +
! style="background:#d0e5f5" | Impact
 +
|-valign="top"
 +
| 1 - Lack of bikes || 4 || 2
 +
|-
 +
| 2 - Missing suppliers || 1 || 3
 +
|-
 +
| 3 - Accidents || 2 || 4
 +
|-
 +
| 4 - Lacking supplies || 1 || 5
 +
|-
 +
| 5 - Sickness or injury || 5 || 2
 +
|}
 +
 
 
== Risk assessment ==
 
== Risk assessment ==
−
Methods to assess identified risks.
+
With the identified risks analysed it is possible to assess them and find the most serious risk.
 +
To get an overview it can be helpful to multiply the impact of the risk with its associated probability.
 +
 
 +
<math>Risk=Impact*Probability</math>
 +
 
 +
If the rating system proposed earlier is used, the risks will be arranged from 1 to 25, with severity increasing with the product.
 +
This is the most basic form of risk assessment.
 +
 
 +
=== The risk matrix ===
 +
[[File:LC-matrix.png|thumb|300px|The probability-impact matrix for risk assessment<ref>[Department of Defense "Risk management guide for DOD acquisition]</ref>]]
 +
When dealing with risks it is normal to prefer several smaller risks rather than one serious risk. This means that the impact of a risk is a little heavier than the probability, which should be taken into account when doing a risk assessment.
 +
To help classifying the risks a matrix has been produced to the right.
 +
Each risk can be plotted into this matrix, where the color code tells the severity of the risk, with red being the most dangerous risks and green the most harmless.
 +
 
 +
Prioritization of the risk should then be carried out within each color-set using the previously defined method to determine the risk's severity. Should two risks have the same severity, the risk with the highest impact rating will be prioritized before the other. When the impact of two risks are the same, they will receive the same level of prioritization.
 +
 
 +
Considerations should be taken when using the matrix, since it has its limitations<ref>[NASA "NASA Risk management handbook"]</ref>:
 +
*The matrix does not consider interactions between two or more risks.
 +
*The matrix does not map uncertainties.
 +
*The matrix' trade-off between likelihood and consequences is fixed and might not suit all projects.
 +
 
 +
=== Example ===
 +
 
 +
With the risk levels determined, Steve makes a risk assesment:
 +
{| class="wikitable collapsible"
 +
! style="background:#d0e5f5" | Risk number
 +
! style="background:#d0e5f5" | Risk assesment
 +
|-valign="top"
 +
| 1 - Lack of bikes || <math>4*2=8</math>
 +
|-
 +
| 2 - Missing suppliers || <math>1*3=3</math>
 +
|-
 +
| 3 - Accidents || <math>2*4=8</math>
 +
|-
 +
| 4 - Lacking supplies || <math>1*5=5</math>
 +
|-
 +
| 5 - Sickness or injury || <math>5*2=10</math>
 +
|}
 +
 
 +
Put into the probability-impact matrix:
 +
[[File:LC-matrix ex1.png|300px]]
 +
 
 +
 
 +
The prioritize list of risks is therefore:
 +
* 5 - Sickness or injury
 +
* 3 - Accidents
 +
* 1 - Lack of bikes
 +
* 4 - Lacking supplies
 +
* 2 - Missing suppliers
 +
 
 
== Risk processing ==
 
== Risk processing ==
−
Methods for mitigating an identified risk
+
When the risks have been determined and assessed, it will be natural to determine what to do about them.
 +
This depends on the previously made risk assessment.
 +
 
 +
===Risk processing using the probability-impact matrix===
 +
 
 +
Any risks in the red area of the matrix should be '''avoided'''.
 +
 
 +
Any risk in the the yellow area should be either '''mitigated, transferred or researched/nurtured''' depending on the malignancy and probability of the risk.
 +
 
 +
Any risk in the green area should most likely be '''accepted'''.
 +
 
 +
However some of the green risks could be yellow, depending on their uncertainty level.
 +
 
 +
===Risk processing without using the probability-impact matrix===
 +
 
 +
If the probability-Impact matrix was not used the following method can be used to determine a risk response:
 +
 
 +
Harmful risk - responses:
 +
 
 +
* Avoid: For high probability, high impact
 +
* Transfer: For low probability, high impact
 +
* Mitigate: For high probability, low impact
 +
* Accept: For low probability, low impact
 +
 
 +
Useful risk – responses:
 +
 
 +
* Accept: For high probability, high impact
 +
* Research: For low probability, high impact
 +
* Accept: For high probability, low impact
 +
* Accept: For low probability, low impact
 +
 
 +
===Risk process responses===
 +
 
 +
Below is a list<ref>[NASA "NASA Risk management handbook"]</ref> of responses and possible solutions to use depending on the probability and impact of the risk.
 +
The list is only a framework. For a defined risk, the actual solution can be found within these frames.
 +
 
 +
 
 +
'''Accept the risk'''
 +
 
 +
Whether the risk is harmful or not, if the probability is low there is no need for doing anything to mitigate it. The occurrence of the event opposed to price of mitigating it will mostly be always turn out to too expensive.
 +
Should a benign risk with a high impact and high probability be determined for a project, then this too should also be accepted, since it is very likely to happen.
 +
 
 +
'''Mitigating the risk'''
 +
 
 +
Malignant risks with low impact, but a frequent occurrence should be mitigated. This is done by making contingency plans, investing in safety equipment and other actions which can lower the probability and/or impact.
 +
 
 +
'''Transfer the risk'''
 +
 
 +
For malignant risks, with a low probability, but high impact, the most reasonably course would be to transfer the risk to someone else. This can be done by outsourcing the risky parts or by buying insurance in case the risk happens.
 +
 
 +
'''Avoid the risk'''
 +
 
 +
Should a risk be harmfully serious and very likely too happen, no insurance company will help. These occurrences should be avoided at all cost. This can be done in numerous ways depending on the risk. The safest way to avoid the risk is to change the part of the project which is in danger. If this is not possible, then the project should either be canceled or delayed until the risk no longer is probability or impact has lessened.
 +
 
 +
'''Research/nurtur the risk'''
 +
 
 +
In the rare cases where a benign risk will have a major impact on a project, but not likely to happen, the risk should be further researched, leading to ways to improve the likelihood. It goes without saying that the cost of implementation should not be larger than the potential gains. If the research proved fruitful the risk should be nurtured to a more probable level.
 +
 
 +
 
 +
=== Example ===
 +
 
 +
Steve then talks for the guys about how to process each risk
 +
 
 +
* 5 - Sickness or injury: Should be transferred. The transfer could be hiring part-time workers or having a temp at hand.
 +
* 3 - Accidents: Should be both mitigated and transferred. The transfer lies in have an insurance, but the consequences of an accident could be lessened by wearing protective gear.
 +
* 1 - Lack of bikes: Should be mitigated. This could be done by have a spare bike ready in case of emergencies, having spare parts for minor repairs and training in repairing the bicycles.
 +
* 4 - Lacking supplies: Should be transferred. Steve suggests that the guys makes a deal with a store, that runs the same wares and make a trade agreement. This way the business is not responsible for the keeping a ready supply.
 +
* 2 - Missing suppliers: Should be accepted. Finding another supplier will only be a problem is the business also lacks supplies.
 +
 
 +
== Risk Monitoring ==
 +
 
 +
With the risk processing is done, the first iteration can be considered concluded.
 +
It is however important to keep monitoring the identified risks and be mindful of need risks which may arise during a project.
 +
When ever a new risk arises it should be sent through the same analysis as the previously determined risks.
 +
 
 +
This will decrease the likelihood of negative impacts on the project, thus encourage a more successful project.
 +
 
 +
=== Example ===
 +
 
 +
After the meeting, Steve tells the other guys to remember to check up on each of the identified risks at least once a month, using a check-list. They also agrees to have a meeting in June to reevaluate the risks and find new risks.
 +
 
 
== Conclusion ==
 
== Conclusion ==
 +
Risk management is an important tool to use, if a successful project is to be achieved.
 +
Risk management should be implemented as early as possible in the process as possible, but does also require recurring follow-ups to ascertain:
 +
*The analysed levels of each risk relates to the current state.
 +
*The effectiveness of the risk response is adequate.
 +
*Newly arisen risks are handled.
 +
 +
= References =
 +
<References/>

Latest revision as of 12:27, 20 December 2018

Developed by Matthias Koch


Risk management strategy as defined be ISO 31000:2009[1]

“When trouble is sensed well in advance in can be easily remedied; if you wait for it to show itself any medicine will be too late because the disease will have become incurable. As the doctors say of a wasting disease, to start with it is easy to cure but difficult to diagnose; after time… it becomes easy to diagnose but difficult to cure.” (Machiavelli, 1514) [2]

When dealing with a project, uncertainties are to be expected, whether the project is influenced by external or internal factors. If an unexpected event turns out to be harmful to the project it is in general terms considered to be a risk. A risk can be defined as the product of the probability of the risk and the impact of the risk. Should a problem be very likely to happen, but have little or no impact on the project there is little reason in prioritizing the mitigation of the problem. For a problem having a high impact, but very low probability the need to mitigate this problem is likewise not a priority. Should a problem be moderately likely and serious, then the problem is a risk and should be handled. The impact of a risk is however more severe than the probability. For instance are smaller impacts, which happen often, easier to accept than heavier impacts, which happen more seldom. The probability of a problem should however not be neglected. A common way to illustrated this is by playing a small game:

In the construction business many factors must by in order for the project to move forward. Six people are given a dice and a problem. Whenever a person rolls a 1 a problem has occurred which delays the project. Thus the probability of a problem happening is 1/6. The probability of no problem happening is:

5/6*5/6*5/6*5/6*5/6*5/6=(5/6)^6=0,33

This means that only a third of the time, the project will progress.

A useful risk management strategy comprises of the following steps:

  • Identify - Potential risks are identified.
  • Analyze - Identified risks are rated, related to probability and impact.
  • Assess - Analyzed risks are ranked and compared to each other to determine which risk to handle first.
  • Process - Solutions are found to counter effect the risks.
  • Monitor - During the project lifetime, identified risks are monitored and new, potential risks are identified.

This article will examine ways to do a successful risk management.

To get a better understanding of the different methods provided in this article, an example has been constructed to show how these are used. The background for the examples are:


Example

Three friends; Adam, John and Fred, wants to start a business together. Their goal is to sell high-quality fruit, pastry and beverage from specially made bicycles in the downtown area. They already have contacts with some suppliers and have already purchased the bikes and other equipment for their trade. During the winter, Fred's cousin, Steve, took a course in risk management and has now offered to help the three friends with their business. This happens in the start of February and the business will launch medio April.


Contents

[edit] Definitions

[edit] Risk

PMBOK defines a risk as: "An uncertain event or condition that, if it occurs has a positive or negative impact on one or more project objectives such as scope, schedule, cost and quality" [3].

Put mathematically: Risk=Impact*probability

[edit] Probability

The probability of a risk is the estimated likelihood of a certain event happening.

[edit] Impact

The impact is the consequences a risk may have on a project. The impact can include: Personal injury, monetary loss, delays, ect.

[edit] Risk identification

During the risk identification, a project is scrutinized for potential risks. During the scrutinisation experience is a good asset when determining the potential risks, but other methods do however exists. Risk identification is the simplest of the risk management steps, since it only requires the project group to think of possible threads and opportunities. Risk identification is however the most important step and should be repeated iterativly during the project lifetime to ensure the safety of the project.

[edit] Identification methods

Instead of relying on experience and common sense, when determining the possible risks, taxonomy-facilitated brainstorming [4] could be used. Brainstorming techniques includes:

These exercises should help the brainstorming and thought processes to identify risks.

Another method[5] is to ask "What could go wrong?", and answer it when relating to the following subjects:

  • Current and proposed staffing, design, process, resources, suppliers, dependencies, operational employment, ect.
  • Monitoring test results
  • Reviewing shortfalls against expectations
  • Analyzing negative trends


[edit] Example

Steve arranges a meeting with the three friend, to discuss possible risks. The group comes up with a lot of possible risks, by telling Steve about their business model and answering his ".. but what if.."-questions. Some of these are listed below:

1. Bicycles are unusable due to wear, damage or theft. This would induce a serious impact on the business since they only have three bicycles and relies on mobility.

2. The remaining suppliers does not sign a contract. Products will either not be available, leading to poorer service or more expensive deals will have to be struck to ensure the right products.

3. Traffic accidents leading to sick days. Since the business revolves around bicycling in a busy city.

4. Suppliers cannot meet demand. The decision to use high quality good, means that changes to increase supply quantities takes a long time to realize.

5. Sickness or injuries. The business relies on that Adam, John and Fred are able to bike in any weather. Should any one of them be unable to work due to sickness or injuries the business will lose a third of it earnings.

[edit] Risk analysis

With the risks identified it is now possible to do a risk analysis. This analysis determines each risk's probability and impact.

[edit] Probability rating

I can be very tricky to determine the exact probability of a given risk and knowing the probability might increase the complexity of the following risk assessment. A standardized way to rate probability is by using the table below[6]. Whether the rating is based on experience, common sense or actual facts does not matter at this step.

Probability level Likelihood Probability
1 Not likely ~10%
2 Low likelyhood ~30%
3 Likely ~50%
4 Highly likely ~70%
5 Near certainty ~90%

Note that a probability of 0% is not possible, since that would mean that the event will not happen.

Likewise is a probability of 100% neither possible, since that would mean that the event will happen.

[edit] Impact rating

Like determining the level of probability of a risk, the level of impact is equally as tricky to determine. There for a rating scale has been presented below[7]. The difference between impact rating and probability rating is that, the impact rating tries to embrace consequences regarding human health, expenses and delays and compare these different subjects. Therefore is a standardized method of determining level of impact useful. Like probability the rating can be based on experience, common sense or actual numbers.

Impact level Technical performance Schedule Cost
1 Minimal or no consequence to performance Minimal or no impact Minimal or no impact
2 Minor reduction in performance or supportability Able to meet key dates Budget or unit production cost increases. <1% of budget
3 Moderate reduction in performance or supportability with limited impact in objectives. Minor schedule slip. Able to meet key milestones with no schedule float. Budget or unit production cost increases. <5% of budget
4 Significant degradation in performance or major shortfall in supportability. May jeopardize success. Critical path affected Budget or unit production cost increases. <10% of budget
5 Severe degradation in performance. Will jeopardize success Cannot meet key milestones Exceeds threshold >10% of budget

[edit] Uncertainty rating

When the probability and impact is determined for a risk, the risk can be assessed. However it would be wise to consider the uncertainty of the analysis. This can be done by using the table below[8].

Uncertainty factor Associated question to be answered
Uniqueness Is this risk issue unique or new compared to risks that have occurred in other projects?
Cross-cutting Character Does this risk issue affect a large number of functions, hardware elements, software elements, or procedures and/or have the potential to cross organizational lines?
Complexity Does this risk issue involve complex interactions between or among hardware elements, software elements, organizations, and/or individuals?
Propagation Potential Could this risk issue lead to a propagation of events that could result in more severe consequences than the immediate events caused by the risk?
Detectability Is there anything that inhibits the ability to detect the full extent of the risk and track its progress?

If a "Yes" is the answer to any of the above mentioned questions, then the risk faces certain uncertainties. These uncertainties should be rated in a manner fitting to group doing the risk analysis. An example might be:

  • The risk's uncertainty is marked Red if two or more questions have gotten a "Yes".
  • The risk's uncertainty is marked Yellow if one question has gotten a "Yes".
  • The risk's uncertainty is marked Green


[edit] Example

Following the example, Steve talks to the three friends about how likely they feel each risk is and what impact it could have. All this, Steve puts into a matrix.

Risk number Probability Impact
1 - Lack of bikes The guys think that this might happen to some times during a season. The bikes are easily replaced or repaired, but this is a bit expensive.
2 - Missing suppliers The guys believe that all contracts are sign before start-up, this is not likely. This could prove to be a moderate set back.
3 - Accidents The friends believe that this is not likely to happen, since they are all experienced cyclists This will have a serious impact.
4 - Lacking supplies Adam, John and Fred does not think is likely to happen However, should the business be out of stock it could take weeks to resupply, which will be a great loss of money.
5 - Sickness or injury It is believed that this is very likely to happen, since non of them are used to biking or being outside for 8 hours. Serious illnesses and traffic accidents aside, this will only have a small impact since it is most likely to only infer a single sick day or two.

Steve determines the risk levels:

Risk number Probability Impact
1 - Lack of bikes 4 2
2 - Missing suppliers 1 3
3 - Accidents 2 4
4 - Lacking supplies 1 5
5 - Sickness or injury 5 2

[edit] Risk assessment

With the identified risks analysed it is possible to assess them and find the most serious risk. To get an overview it can be helpful to multiply the impact of the risk with its associated probability.

Risk=Impact*Probability

If the rating system proposed earlier is used, the risks will be arranged from 1 to 25, with severity increasing with the product. This is the most basic form of risk assessment.

[edit] The risk matrix

The probability-impact matrix for risk assessment[9]

When dealing with risks it is normal to prefer several smaller risks rather than one serious risk. This means that the impact of a risk is a little heavier than the probability, which should be taken into account when doing a risk assessment. To help classifying the risks a matrix has been produced to the right. Each risk can be plotted into this matrix, where the color code tells the severity of the risk, with red being the most dangerous risks and green the most harmless.

Prioritization of the risk should then be carried out within each color-set using the previously defined method to determine the risk's severity. Should two risks have the same severity, the risk with the highest impact rating will be prioritized before the other. When the impact of two risks are the same, they will receive the same level of prioritization.

Considerations should be taken when using the matrix, since it has its limitations[10]:

  • The matrix does not consider interactions between two or more risks.
  • The matrix does not map uncertainties.
  • The matrix' trade-off between likelihood and consequences is fixed and might not suit all projects.

[edit] Example

With the risk levels determined, Steve makes a risk assesment:

Risk number Risk assesment
1 - Lack of bikes 4*2=8
2 - Missing suppliers 1*3=3
3 - Accidents 2*4=8
4 - Lacking supplies 1*5=5
5 - Sickness or injury 5*2=10

Put into the probability-impact matrix: LC-matrix ex1.png


The prioritize list of risks is therefore:

  • 5 - Sickness or injury
  • 3 - Accidents
  • 1 - Lack of bikes
  • 4 - Lacking supplies
  • 2 - Missing suppliers

[edit] Risk processing

When the risks have been determined and assessed, it will be natural to determine what to do about them. This depends on the previously made risk assessment.

[edit] Risk processing using the probability-impact matrix

Any risks in the red area of the matrix should be avoided.

Any risk in the the yellow area should be either mitigated, transferred or researched/nurtured depending on the malignancy and probability of the risk.

Any risk in the green area should most likely be accepted.

However some of the green risks could be yellow, depending on their uncertainty level.

[edit] Risk processing without using the probability-impact matrix

If the probability-Impact matrix was not used the following method can be used to determine a risk response:

Harmful risk - responses:

  • Avoid: For high probability, high impact
  • Transfer: For low probability, high impact
  • Mitigate: For high probability, low impact
  • Accept: For low probability, low impact

Useful risk – responses:

  • Accept: For high probability, high impact
  • Research: For low probability, high impact
  • Accept: For high probability, low impact
  • Accept: For low probability, low impact

[edit] Risk process responses

Below is a list[11] of responses and possible solutions to use depending on the probability and impact of the risk. The list is only a framework. For a defined risk, the actual solution can be found within these frames.


Accept the risk

Whether the risk is harmful or not, if the probability is low there is no need for doing anything to mitigate it. The occurrence of the event opposed to price of mitigating it will mostly be always turn out to too expensive. Should a benign risk with a high impact and high probability be determined for a project, then this too should also be accepted, since it is very likely to happen.

Mitigating the risk

Malignant risks with low impact, but a frequent occurrence should be mitigated. This is done by making contingency plans, investing in safety equipment and other actions which can lower the probability and/or impact.

Transfer the risk

For malignant risks, with a low probability, but high impact, the most reasonably course would be to transfer the risk to someone else. This can be done by outsourcing the risky parts or by buying insurance in case the risk happens.

Avoid the risk

Should a risk be harmfully serious and very likely too happen, no insurance company will help. These occurrences should be avoided at all cost. This can be done in numerous ways depending on the risk. The safest way to avoid the risk is to change the part of the project which is in danger. If this is not possible, then the project should either be canceled or delayed until the risk no longer is probability or impact has lessened.

Research/nurtur the risk

In the rare cases where a benign risk will have a major impact on a project, but not likely to happen, the risk should be further researched, leading to ways to improve the likelihood. It goes without saying that the cost of implementation should not be larger than the potential gains. If the research proved fruitful the risk should be nurtured to a more probable level.


[edit] Example

Steve then talks for the guys about how to process each risk

  • 5 - Sickness or injury: Should be transferred. The transfer could be hiring part-time workers or having a temp at hand.
  • 3 - Accidents: Should be both mitigated and transferred. The transfer lies in have an insurance, but the consequences of an accident could be lessened by wearing protective gear.
  • 1 - Lack of bikes: Should be mitigated. This could be done by have a spare bike ready in case of emergencies, having spare parts for minor repairs and training in repairing the bicycles.
  • 4 - Lacking supplies: Should be transferred. Steve suggests that the guys makes a deal with a store, that runs the same wares and make a trade agreement. This way the business is not responsible for the keeping a ready supply.
  • 2 - Missing suppliers: Should be accepted. Finding another supplier will only be a problem is the business also lacks supplies.

[edit] Risk Monitoring

With the risk processing is done, the first iteration can be considered concluded. It is however important to keep monitoring the identified risks and be mindful of need risks which may arise during a project. When ever a new risk arises it should be sent through the same analysis as the previously determined risks.

This will decrease the likelihood of negative impacts on the project, thus encourage a more successful project.

[edit] Example

After the meeting, Steve tells the other guys to remember to check up on each of the identified risks at least once a month, using a check-list. They also agrees to have a meeting in June to reevaluate the risks and find new risks.

[edit] Conclusion

Risk management is an important tool to use, if a successful project is to be achieved. Risk management should be implemented as early as possible in the process as possible, but does also require recurring follow-ups to ascertain:

  • The analysed levels of each risk relates to the current state.
  • The effectiveness of the risk response is adequate.
  • Newly arisen risks are handled.

[edit] References

  1. ↑ [ISO 31000:2009]
  2. ↑ [Niccolo Machiavelli “The Prince”]
  3. ↑ ["A Guide to the Project Management Body of Knowledge ( PMBOK® Guide )—Fifth Edition"]
  4. ↑ [NASA "NASA Risk management handbook"]
  5. ↑ [Department of Defense "Risk management guide for DOD acquisition]
  6. ↑ [Department of Defense "Risk management guide for DOD acquisition]
  7. ↑ [Department of Defense "Risk management guide for DOD acquisition]
  8. ↑ [NASA "NASA Risk management handbook"]
  9. ↑ [Department of Defense "Risk management guide for DOD acquisition]
  10. ↑ [NASA "NASA Risk management handbook"]
  11. ↑ [NASA "NASA Risk management handbook"]
Retrieved from "http://wiki.doing-projects.org/index.php?title=Risk_management_strategy&oldid=60581"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox