Controlling a stage

• Purpose
• Objective
• Context
• Activities
  • Overview
  • Authorize a Work Package
  • Review Work Package status
  • Receive completed Work Packages
  • Review the stage status
  • Report highlights
  • Capture and examine issues and risks
  • Escalate issues and risks
  • Take corrective action

Key sections

• Introduction
• Business case
• Organization
• Quality
• Plans
• Risk
• Change
• Progress
• Introduction to processes
• Starting up a projectDirecting a project
• Initiating a project
• Controlling a stage
• Managing Product Delivery
• Managing a Stage Boundary
• Closing a Project
• Tailoring PRINCE2 to the project environment
• Directing Projects with PRINCE2

Activities

Receive completed Work Packages

Where work has been allocated to individuals or teams, there should be a matching confirmation that the work has been completed and approved.

Once approved, any subsequent changes to the product(s) must pass through change control (see the section covering ‘Change’).
This should be an automatic part of any configuration management method being used.

Diagram 1 shows the inputs to, and outputs from, this activity.

© Crown copyright 2005 Reproduced under licence from OGC

Diagram 1

PRINCE2® recommends the following actions:

• Ensure that the Team Manager has completed the work defined by the Work Package(s)
• Check that the Quality Register entries relating to the product(s) are complete
• Ensure that each product in the Work Package has gained its requisite approval (as defined in the quality responsibilities in its Product Description)
• Confirm that the Configuration Item Record for each approved product has been updated
• Update the Stage Plan to show the Work Package as completed

Diagram 2 shows the responsibilities for this activity.

© Crown copyright 2005 Reproduced under licence from OGC

Diagram 2

PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.