home

Articles

Blog

Books

Tools

Links

FAQ Page


Controlling A Stage CS

Google
 
Web www.software-risk.co.uk

A process in the PRINCE2 project management methodology. It concerns the day-to-day management of a stage by the Project Manager.

What is it? The project manager has the authority to run the project, day to day on behalf of the Project Board. The Controlling a Stage (CS) process is the construct in which this is handled.

The aims of the stage are:-


 *Allocate work to individuals and/or teams
 *Check on progress
 *Quality assurance
 *Change control
 *Progress reporting
 *Detect plan deviations
 *Risk monitoring
 *Monitoring for issues that may impact on the business case.

Why? Although the project manager has control of the day-to-day running of the project, the work still has to be conducted within a structured framework

The project manager also needs to know who will do the work and when it will be done. Then he needs to keep track of progress and prepare to keep the project board updated.

Who The project manager quite clearly is the main person.

A number of other people are involved though in making the process work. The project board triggers the process by the sub-process Authorising a Stage or Exception Plan.

Then there are the people or teams actually allocated the Work Packages. Finally the people who feed the information back up and collate it forthe project manager to write reports.

How As with all the processes in PRINCE2, CS is split into sub-processes.


 *Authorising a Work Package (CS1)
 *Assessing Progress (CS2)
 *Capturing Project Issues (CS3)
 *Examing Project Issues (CS4)
 *Reviewing Stage Status (CS5)
 *Reporting Highlights (CS6)
 *Taking Corrective Action (CS7)
 *Escalating Project Issues (CS8)
 *Receiving Completed Work Packages (CS9)

A number of management products should result from the process.


 *Work package
 *Highlight Report
 *Exception Report
 *Project Issues
 *Updated Stage Plan

As with everything in PRINCE2, not all projects will need all these sub-processes to be worked through exhaustively. The level to which each one is conducted should be appropriate to the project undertaken. The consequences of not doing so is that PRINCE2 becomes a box-ticking exercise.

Related Articles
Mercury Change Management Control
Euroequity issues
A-D
Managing Stage Boundaries
Closing A Project
Managing Product Delivery
Xansa and Tesco Outsourcing
ITIL - Request For Change (RFC)

Similar Areas

Process Improvement Items

Project Management Items

Risk Management Items

Sarbanes-Oxley Items

Management Items

Selected Books

Keywords

PRINCE2

PRINCE 2

Prince2 process

project management

project manager

stage

controlling a stage

CS

CS1

CS2

CS3

CS4

CS5

CS6

CS7

CS8

CS9

project board

allocate work

quality assurance

change control

progress report

plan deviation

risk monitoring

business case

business case impact

Authorising a Stage

Exception Plan

sub-processess

PRINCE2 process

work package

authorising a work package

assessing progress

project issues

issues

examining project issues

stage status

escalating project issues

highlight report

exception report

stage plan


See our Sarbanes-Oxley compliance, load testing and Financial Glossary pages.
Articles   Books   FAQ Page   home   Jobs   Links   Reviews Page   Tools  
Booklist   books   Measurement   Testing   Tools