Managing Project Risks and Issues
Inherent (or Company) Danger
Inherent Danger is the danger that exists in the atmosphere about your portal undertaking. It will tend to be unique to your organisation it’s culture and politics. For example, if you have a fragmented company (both geographical or functional), then this will produce a greater inherent danger of bad communication.
Project (Particular) Danger
Project Danger is the danger specific to your undertaking. Some Project Danger stems from the nature of what you are doing there are certain risks common to any undertaking (e.g. the unfamiliarity to customers of the technology you are deploying). However, most undertaking danger is beneath your direct affect for example the abilities of the undertaking group, the level of governance usefulness and so on.
Stage Danger
Finally, there is ‘stage risk’ which is the danger associated with the specific activity of any offered phase of the undertaking plan.
The Danger Log & Danger Strategy
In purchase to stay in manage of the risks to your portal undertaking, it tends to make perception to have a formal log of all risks, to which anybody involved with the undertaking is entitled to add. You may use a formal workshop to initial populate the log.
Assessing Dangers
Every danger (nevertheless derived) can be assessed using a easy methodology, whereby the probability of the danger being realised (‘likelihood’) and the size of the effect on the undertaking objectives (‘severity’) can be measured.
The easiest system (primarily based on the PRINCE undertaking management technique) is to give a score of one-3 for likelihood and severity (exactly where one is reduced and 3 is higher). From these scores, the importance of every danger can be measured as the item of likelihood and severity.
Clearly, any danger of importance 9 demands immediate attention, followed by risks rated six and so on.
Danger Counter-measures
The importance of every danger ought to be frequently maintained, primarily based on the extent to which the likelihood and severity of effect alter more than time.
For every danger, 1 ought to enter a counter-measure in the danger plan. Exactly where a danger can be eradicated, then this will be the counter-measure. Exactly where it cannot be fully eradicated, then danger mitigation actions will be the most appropriate.
Issues Log
A Danger is something that is however to happen, while an Issue is something that has already happened. It might well be convenient to use the Danger Log to also track any issues on the undertaking. Issues will usually fall into 1 of the subsequent categories:
(R) – Request for a alter (in the scope of the undertaking)
(O) – An item has been recognized that is Off-Specification
(Q) – A Question has been raised that requirements to be resolved
(S) – A Statement of Problem has been raised by somebody and
(I) – Other issues.
To score issues, just ascribe an importance score (of between one and 9).
Managing Dangers and Issues
Once you have place a Strategy in location, then it is essential to frequently keep track of and report on the counter-measures that have been deployed and whether or not or not they have been effective in reducing the overall danger profile of the undertaking.
For templates and examples of risks and issues pertinent to intranet portal deployment tasks, make sure you check out my chapter on Managing Risks and Issues in the (totally free to entry) Intranet Portal Manual.
If you act, handle and report frequently on risks and issues, you will have substantially enhanced your chances of undertaking good results!
About the author:
David Viney (david@viney.com) is the author of the Intranet Portal Manual 31 pages of advice, tools and downloads covering the time period prior to, during and following an Intranet Portal implementation.
Study the manual at http://www.viney.com/DFV/intranet_portal_guide or the Intranet Watch Weblog at http://www.viney.com/intranet_watch.