What is it?
A programme risk register is a vital tool which makes risk management possible. It is the central place where all a project or programmes risks are aggregated together and tracked. This risk register has the capability to log not just risks which threaten the programmes success, but also opportunities in accordance with MSP best practice.
The difference between this log and Project Risk logs we offer for download on this site is that this log is designed specifically to manage risks which have strategic impact on a programmes probability of success /failure and follows the best practice guidelines as detailed in MSP/P3O.
So what is an Inter Project Dependency (IPD)?
It is where Projects become so intertwined that one portion of one project cannot begin or be continued unless a part of another project has been completed.
Alternatively, it can be described as the relationship between a key event in a Controlling project and another key event in a Dependent project.
How do you introduce risk & issue management into your project?
• Stage 1 Set-up a Project Organisation
- Designate a Project Sponsor
The first thing to do is designate someone as your project sponsor who will ultimately be responsible for the success or failure of the project, and as such will have authority over all the participants involved in the project, whether they are IT or business related professionals.
This is a question, which I have rarely seen properly answered in any PRINCE II manual.
As with many things in life, the theory and the practical application of a concept are often two distinct sides of the same coin, which can lead to some serious difficulties. Over the years, I have audited many projects /programmes of work and most, if not all, of those which were subsequently discovered to be failures were characterised by poor /non-existent risk & issue management.
More often than not the project /programme managers responsible for these process failures, when challenged, refuse to accept that they had been running a project /programme of work with little, if any, risk and issue management present.
Please click FREE Risk & Issue Log
These logs have been updated and improved as of 14/10/08 and now include an automatic risk & issue mitigation /resolution overdue date indicator. This means that for each risk /issue the sheet calculates how many days overdue from any given target resoltuion /mitgation date as compared with the current date. This kind of feature comes into its own when used in conjunction with our new Project Status Report due out later today IT Project Status Report.
These template logs contain some content from a real project so that you can get a feel for how to use them as part of an effective set of risk and issue management processes.
If you are wondering how to make risk and issue management work for you then I suggest you read the following How to make risk and issue management work ?