|
IT Bites > Services >
Project Management > Control
Defined by the Project Managers Institute as:
| |
"ensuring that project objectives are met
by monitoring and measuring progress and taking corrective action when
necessary" |
|
IT Bites principle activity once the project is under way is to provide
control This revolves around ensuring that planned work progresses to target
and, when it does not, planning for correction.
Control requires that:
 | Work is issued in a timely and efficient manner supported by documentation
e.g signed off |
| Progress is constantly maintained and assessed e.g. status reporting |
| Project issues are captured, assessed and, if necessary escalated, and
finally resolved |
| Project governance is kept informed about successes as well as problems |
| Corrective actions are properly planned and, if appropriate, signed off |
| Completed work is formally recognised |
Where a project involves more than one stage, the boundaries (or gateways) between each
must also be carefully managed:
| Each stage will have it's own project plan (Stage Plan) which will be
prepared with the same techniques as Project Planning |
| The Project plan itself may require updating |
| The Business Case may be reviewed for continuing validity |
| The Risk Log is updated |
| End of one stage is formally agreed and approval for the next to start is
sought |
In Prince 2 terms, Control corresponds to the Controlling a Stage (CS) and
Managing Stage Boundaries (SB) processes.
|
