Overview
Controlling a Stage outlines the process used by the Project Manager to carry out the day to day tasks of a project. This is not a prescriptive process - many sub-processes in Controlling a Stage will be triggered when the need arises. The 'soft' skills of project management, although important throughout are particularly relevant here because the Project Manager must manage the allocation of work to Team Managers, evaluation of their work, and report on that work carried out so far to the Work Package.
In the case of a small project with a flat management structure where the Project Manager is also the Team Manager Work Packages may be handed directly to, and negotiated with, the Project Team members.
Responsibility in Controlling a Stage lies solely with the Project Manager who must ensure all work is delivered within the required quality, budget and time constraints.
Tips
Notes
- Outlines the day-to-day responsibilities of the Project Manager including:
- Allocating work
- Checking progress
- Ensuring quality
- Managing changes
- Monitoring risks
- Reporting progress
- Watching deviations
- This is an event driven process often triggered in an ad hoc manner
- Commences after DP3 Authorising a Stage or Exception Plan
- This set of processes ensures that "work during a stage commences and continues with the consent of the Project Manager" who, in turn, has consent from the Project Board
- The general sequence of events is:
- Objectives:
- Ensure the correct products are created to the expected quality levels
- Managed within Tolerances
- Sensible utilisation of resources
- Manage deviations from the Stage Plan
- Ensure either a redirection or halt of the project if the Business Case is compromised
- Reports created:
Case studies and examples
Related links
|
