« Terms for Measuring Benefits for ProjectsOne Lesson of Death »

Risk Management in Projects

01/20/05 | by Clarise | Categories: Project Management

Many projects get off track or even fail. Many of us have heard the familiar story that Company X spent millions of dollars on an IT project that was never implemented. One project management task that I’ve seen often neglected is Risk Management. Hence, I thought I’d blog about it &#59;D

While managing projects, it is important to be able to prepare for the effects of any uncertain event affecting the project for good or for bad.

To manage risks in projects, it is important to do (1) Risk Management Planning and (2) Risk Management and Control.

1. Risk Management Planning involves:

a. identification of risks that will affect the project. During this identification process, it is important to note what the risks are and the possible triggers.

b. analysis of risks - After identification is done, analyzing the effects of the risks qualitatively and quantitatively provides a good information on the business impact of the risk event.

There are different techniques one can use. One is creating and utilizing a Project - Risk questionnaire with a scoring system. With a scoring system, one can score the risk effect. Hence, one can identifiy what are the highest risk events and create a corresponding strategy. The diagram below is an excerpt of a sample questionnaire.

Other techniques include Business Impact Evaluation, Decision Tree Analysis and if one wants to be even more sophisticated, maybe a Monte Carlo Simulation Analysis. :P

c. creation of Risk response - Of course, after all the analysis, a strategy on how to respond to the risk is the next logical step. This helps to avoid or mitigate the effects.

2. Risk Management and Control: After Planning always comes implementation. Risk management and control involve looking at the risks that have been identified and executing the plan. This process involves careful monitoring to ensure that the plan is implemented and improved if necessary. Workarounds and corrective action may have to be done as well as ensuring that if changes need to be made, that the triggering event does not cause an adverse ripple effect on the project.

I don't want this to be too long a blog. One thought I'd like to leave is: One must remember that the project manager needs to work with its project team, project sponsors and users to implement effective risk management in projects. After all, a project is always a team effort.

Send feedback »

No feedback yet

August 2020
Mon Tue Wed Thu Fri Sat Sun
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
 << <   > >>
This blog contains thoughts that range from non-technical to technical. Its name is derived from "Yakity Blah Blah" a column I once had that discussed a cornucopia of ideas. Who am I? I'm Clarise Z. Doval Santos, providing Project Management and Technical Leadership for data management and analytic, data science, IoT and sensor analytics ecosystems 37.652951177164 -122.490877706959


  XML Feeds

blog soft

An unexpected error has occurred!

If this error persists, please report it to the administrator.

Go back to home page

Additional information about this error:

MySQL error!

Incorrect key file for table './tiapress/tiap_hits__aggregate.MYI'; try to repair it(Errno=126)

Your query: Aggregate hits log

REPLACE INTO tiap_hits__aggregate ( hagg_date, hagg_coll_ID, hagg_type, hagg_referer_type, hagg_agent_type, hagg_count )
SELECT DATE( hit_datetime ) AS hit_date, IFNULL( hit_coll_ID, 0 ), hit_type, hit_referer_type, hit_agent_type, COUNT( hit_ID )
  FROM tiap_hitlog
 WHERE hit_datetime < '2020-08-04 00:00:00'
 GROUP BY hit_date, hit_coll_ID, hit_type, hit_referer_type, hit_agent_type