Component Controls
From IT frameworks
Component Controls
Controls ensures decisions can be made on how to proceed with the project. The use of Controls ensures the project can proceed as long as it is viable to the Business Case and remains within defined resources.
Controls ensure the different levels of management in the PRINCE2 method can monitor the projects progress. The Project Board shall manage by exception in PRINCE2. This means that Stage Plans are approved with defined resources. Any forecast outside these resources would call in the Project Board. As long as the resources used are under the Tolerance level, the Project Manager may proceed as planned.
PRINCE2 emphasises a control loop of ‘Plan’; ‘Monitor’; ‘Control’. Most controls in PRINCE2 are event-driven, including all the decision making ones. Highlight Reports and Checkpoints/Checkpoint Reports are the only ‘time-driven’ controls in PRINCE2.
The major controls for the Project Board:
- Project Initiation Document: (Shall the project be allowed to initiate based on resources, risk, time, quality etc.)
- End Stage Assessment: (Is the Business Case still viable and is the project still on track)
- Highlight Reports: (Regular reports during a stage)
- Exception Reports: (A forecast that tolerance levels will be exceeded)
- Exception Assessment: (The Project Board consider what course of action to take in relation to the Exception Report)
- Project Closure: (Is it proper to close the project? Any follow-on actions needed?)
Work Packages are also Controls the Project Manager defines to Team Managers with defined resources to be used. The Team Manager reports to the Project Manager through Checkpoint Reports.
Controls are always visible in PRINCE2 projects. Controls are in place to allow a smooth running of the project if everything goes to plan. i.e. stays within the tolerances defined in the Business Case.
