Managing Project Risks

January 23, 2010 | Author: PM Hut | Filed under: Risk Identification, Risk Management, Risk Quantification & Analysis, Risk Response & Control

Managing Project Risks (#28 in the Hut Introduction to Project Management)
By JISC infoNet

All projects bring with them an element of risk. In the best-planned projects there are uncertainties and unexpected events can always occur for example project staff might leave unexpectedly, the budget might suddenly be cut or a fire or theft might affect the project progress. The majority of risks are however related to the fact that your plan is based on estimates and they are therefore manageable. Risk management is a mechanism to help you to predict and deal with events that might prevent project outcomes being delivered on time.

Risk management is probably the single most important part of project management.

Identifying Project Risks

You will undertake an initial risk assessment as part of starting up the project. Basically you are asking the questions:

  • What could possibly happen to affect the project?
  • What is the likelihood of this happening?
  • How will it affect the project?
  • What can we do about it?

The sort of areas you will be looking at for associated risks are:

  • the activities along the timeline and any threats to completion and to timescales
  • the project components: people, equipment, infrastructure requirements, other resources
  • dealings with contractors and suppliers
  • other projects that might have an impact
  • organisational changes that might take place during the project
  • outside influences that might affect the project such as changes in funding, government policy or the requirements of a funding body

Greatest risk often occurs where there is some sort of interface. This may be an interface between systems, departments, processes or organisations.

The assessment of likelihood of the risk occurring and potential impact if it does occur will come from the experience and knowledge of project stakeholders and others consulted during the risk analysis process. In other words, identifying risks is best done as a team effort. People with different skills, experiences and specialisms will see individual risks differently and you want a balanced, rather than a biased, analysis.

You can think of risks in terms of a matrix:

Risk Probability vs Impact

Risk Probability vs. Impact

Your greatest effort will be focussed on addressing the risks that are most likely to occur and those that will have the biggest impact if they do occur.

Recording Project Risks

You will need to maintain a risk log or register. This should record:

  • A description of the risk
  • The likelihood of the risk occurring
  • The potential impact of the risk
  • Details of mitigating actions to be taken
  • Identification of any early warning signs that indicate the risk is about to occur
  • The risk owner
  • Details of any contingency plans where applicable

In order to effectively manage risk it is important that each risk is allocated to an identified owner. This should be someone within the project team whose responsibility it is to keep an eye on the situation and ensure that the necessary mitigating actions are actually carried out. Responses to the initial risk assessment may include:

  • Risk Transfer - move the risk to someone more able to deal with it e.g. contract out the supply and support of the hardware infrastructure.
  • Risk Deferral - alter the plan to move some activities to a later date when the risk might be lessened e.g. wait till a statutory change has ‘bedded-in’ before changing a related process.

  • Risk Reduction - Either reduce the probability of the risk occurring or lessen the impact e.g. increase staffing resource on the project.

  • Risk Acceptance - Sometimes there’s not a lot you can do other than accept the risk and ensure that contingency plans are in place.

  • Risk Avoidance - Eliminate the possibility of the risk occurring e.g. use alternative resources or technologies.

Managing risk is an ongoing process. The nature of the risks you are facing will alter as the project progresses e.g. staff recruitment may be a big issue at the start of a project whereas staff retention is the issue as the project draws near to an end. At the very minimum you should review your risk assessment and management plan at each stage boundary before moving into the next stage of the project.

JISC infoNet aims to be the UK’s leading advisory service for managers in the post-compulsory education sector promoting the effective strategic planning, implementation and management of information and learning technology.

Share this article:
  • Facebook
  • LinkedIn
  • TwitThis

1 person has left a comment

Interesting post.

I just did a podcast with a guy from Epicor about mitigating risk on IT projects - http://ow.ly/10bqB

I find it it interesting that different organizations have vastly different risk tolerances. Acceptable risk for some is completely unacceptable for others.

Can you comment on risk as it pertains to an organization’s culture?

Phil Simon wrote on January 25, 2010 - 11:15 am | Visit Link

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Project Management Categories