Project Smart ~ Exploring trends and developments in project management today

Calendar icon
Adobe PDF icon

Tracking a Risk

~ By Kenneth Darter

Dial showing three levels of risk management

Risk management is a vital part of project management. Every project carries some element of risk. Being able to deal effectively with these risks (whether they be negative or positive) can be what makes or breaks a project in the end. The result of all risk management should be the ability to track a risk from beginning to end. Whether a project uses a formal risk process with automated tools or just a shared Excel file on a common drive, the risks must be tracked very carefully by the project management team.

1. Creation

The creation of the risk is the first step and oftentimes, the step in which a risk can be easily lost. Risks may come up in meetings or in emails or even in hallway conversations. The project manager needs to make sure that everyone on the project knows what a risk is and what to do when they identify a potential risk. There should be one person or team that is responsible for creating the risk and starting the tracking process once a risk has been identified by someone in the project team. While they may not see the risk as something that needs to be tracked, it should be up to the project manager and the steering committee (or other decision making body) to determine if the risk needs to be tracked and followed through the risk lifecycle.

2. Evaluation

Once a risk is created, then the project manager or designated team needs to evaluate it. Usually, this involves determining the likelihood or the probability of the risk occurring and then determining the impact of the risk on the project. There may be other evaluations called for in the Project Charter or formal risk management document. This step is important in that it helps the decision makers determine what needs to be done about the risk. Research and homework must be done by the designated person so that the evaluation will be truly useful and not just a rough estimate.

3. Mitigation

Once the creation and evaluation of the risk is done, it is time to execute the mitigation plan for the risk. Note that mitigation steps can be done for positive or negative risks. The mitigation includes any steps that the project team has decided to take in order to prevent the risk or minimise the impact of the risk. It may be that the team decided to do nothing, or it may be that there is a whole separate plan to deal with the risk with its own scope and resources beyond the original project. All of this depends upon the evaluation and the decisions made by the risk committee or stakeholders. The risk and all the mitigation steps must be monitored carefully through this entire process.

4. Dispensation

The last step in tracking the risk is to record the dispensation of the risk. Was the risk accepted or was there a mitigation plan and if there was a mitigation plan, was it successful? Along with the actions that were taken about the risk, the dispensation should include the lessons learned by the project team about the risk. That way, the next time this risk is identified or observed by the project team, they will not have to start from scratch and go through these steps.


Comments

Be the first to comment on this article.

Add a comment



(never displayed)



 
2000
Type the word for the number 5.
Notify me of new comments via email.
Remember my form inputs on this computer.

Who is the Project Manager?

Businessman illustrating a project managers key role

A dilemma: should you appoint someone who is an experienced project manager or someone who will champion the change?

What Is the Mission of Your Project?

Illustration of a blackboard showing words Mission Statement

The stakeholders in a project can have lots of different goals, but a software project is more than just the sum of its parts.

Soft Power for Success

Businessman touching a power button

Soft power is the ability to get people to work with you by attracting them to be part of what you stand for; rather than to coerce, force or pay them.

Successful Projects: It's Not Rocket Science

A woman with pen in hand standing next to an image of a rocket

Avoiding the common pitfalls of IT project management is not rocket science; it is simply a case of taking some sensible measures.

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates and opinion on what's happening in the world of project management.


Latest Comments

Kelly D commented on…
Managing Small Projects
- Thu 19 January 4:45pm

Sean H commented on…
Better Coaching Using the GROW Model
- Thu 19 January 3:43pm

Jeda commented on…
Project Planning a Step by Step Guide
- Tue 17 January 11:50am

Latest tweets

Managing Small Projects https://t.co/kLmCdOgGMJ An excellent summary of basic project management. #projectsmart #pmot #pm about 18 hours ago

General Project Management • Newbie needing some advice https://t.co/R3kO7SHsUv #projectsmart #pmot about 1 day ago

General Project Management • Re: Junior PM needs advice - potentially being moved to a project… https://t.co/vJMX8Atrw1 #projectsmart #pmot about 6 days ago