PRINCE2
In PRINCE2 methodology, controlling a project relates to the following component and sub-processes:
- Controls
- Authorising Initiation (DP1)
- Authorising a Project (DP2)
- Authorising a Stage or Exception Plan (DP3)
- Confirming Project Closure (DP5)
- OGC PRINCE2 website
Controlling A Project
Having set up your reporting and review mechanisms you also need control mechanisms to help you identify and deal with the things that come from 'left of field' to throw your project off-course. Here we will discuss how to deal with Risks, Issues and Changes. We have also included project Quality in this section as this should also be the subject of clear control procedures. The word 'control' can itself be a challenge in some cultures so feel free to brand the techniques in a way that suits your environment.
Change control in this section refers to suggested or actual changes or amendments to the project itself – not any necessary changes to business processes or ways of working required as part of the project (this is the subject of a separate infoKit on Change Management). For this reason we have termed it Managing Scope.
The logs that will help you manage Risk, Issues, Scope and Quality require setting up during the start-up phase of the project. The ongoing process of project control is however part of the iterative cycle of project management.
Resources
