|
|
|
|
| Tools
|
|
|
|
|
|
Template for a Project Status Report
|
|
|
|
|
|
The Project Status Report is designed to update all project stakeholders on the current projects status. It is unlikely
that any stakeholder will have a detailed understanding of the whole project. The report is intended to provide a broad
high-level update, clearly identifying when things are not going to plan or if it is anticipated that this may happen. The
report will be used as the basis for the senior project team approving any changes to the project plan.
The report will be produced at a frequency agreed by the project board or steering team – often once a month.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project Initiation Document: Evaluation Centre
|
|
|
|
|
|
Successful projects are rare because every project encompasses a unique set of circumstances, business issues and
people. There will inevitably be unforeseen problems, technical hold-ups and mis-communications, so it is best practice
to establish as many of the ground rules as possible before starting. Putting them in a document ensures they are clearly
defined and accessible to everyone involved in the project.
This document is sometimes called the Project Charter and it lays out the ground rules for running an approved project -
ie, once the feasibility and business case for the project have been established.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Templates for a Risk Register
|
|
|
|
|
|
The Risk Register defines a set of identified risks to achieving the business benefits associated with the project. The
register contains plain English descriptions of possible outcomes that differ from the desired outcomes of the project.
The templates should be used as part of a risk management process (see ‘A Guide to Risk Management’ for
more details).
The Risk Register will contain an entry for each identified risk. It will be used as a repository of known risks and
associated actions to mitigate them. It is a dynamic document that will change as risks pass, new risks are identified or
the impact of risks change as the project evolves.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Guide to Risk Management
|
|
|
|
|
|
This document provides an overview of project risk management. It shows the benefits to be gained and how they may
be achieved. A key element of risk management is the development of a Risk Register of all anticipated threats to the
project. This document outlines how a Risk Register can be created.
Depending on the size and complexity of project, risk management may be a formal and detailed process, or totally
informal: whichever approach is taken, it should not be ignored.
Risk management is about harnessing the knowledge and ability that already exists within the business, to maximise
certainty about the outcome of your project.
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|