Controlling a Stage

From IT frameworks

Contents 1 Controlling a Stage (CS) 1.1 Purpose & Description 1.2 Objectives 1.3 Inputs 1.4 Outputs 1.5 Hints and Tips 2 Sub-processes

Controlling a Stage (CS)

Purpose & Description

• This process covers the day to day management of the Project.
• Once a Stage Plan has been approved, Controlling a Stage is triggered.
• This process may be described as the controlled middle.
• This process drives the Managing Product Delivery process (MP) with work package input (CS1) and receives completed work packages back again to CS9.

Objectives

• To deliver the agreed products.
• To keep control over time, cost & quality.
• To keep stakeholders informed on progress.
• Authorise work.
• Monitoring work.
• Reviewing work.
• Taking any necessary corrective action.

Inputs

• Authorisation to proceed from Project Board.
• Project Brief & Initial Stage Plan.

Outputs

• PID to DP2
• Next Stage Plan to DP3.

Hints and Tips

• For small projects both SU & IP can be combined. Then the output to Project Board should be the Project Brief + Initial Stage Plan = PID yet still ensuring the Project Board receive the necessary information.

Sub-processes

• CS1 Authorising Work Package
• CS2 Assessing Progress
• CS3 Capturing Project Issues
• CS4 Examining Project Issues
• CS5 Reviewing Stage Status
• CS6 Reporting Highlights
• CS7 Taking Corrective Action
• CS8 Escalating Project Issues
• CS9 Receiving Completed Work Package