For training call +44(0)1273 622272

Your basket is empty View Cart shopping cart

theBLOG

Controlling a Stage (CS) PROCESS

Written by Andy Trainer – Thu 12 Jul 2007

PRINCE2® PROCESSES – Controlling a Stage (CS)

The purpose of the Controlling a Stage process is to assign work to be done, monitor such work, deal with issues, report progress to the Project Board, and take corrective actions to ensure that the stage remains within tolerance.

For each stage, the following cycle of activities will be covered:

  • Authorise 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 correction action

The continued assessment of risk and issues during this process is important.

Products used or produced during this process:

  • Work packages, detailing the products to be produced must be agreed between Project and Team Manager.
  • Quality register – checked for approved products produced
  • Configuration item records – updated with the latest status of products
  • Checkpoint reports – reviewed in preparation for Highlight reports
  • Highlight Reports (time-driven control) produced by the Project Manager, sent to the Project Board advising on progress information.
  • Issue reports and Issues register in which all issues are captured and examined.
  • Daily log – used to informally manage any risks and issues
  • Lessons Log – updated with any lessons learned during the stage
  • Updated Risk register.
  • The Stage Plan which is regularly updated with actual achievements.
  • An Exception Report may also need to be created if an issue is forecast to exceed stage tolerances.

Learn more about the Controlling a Stage Process on our PRINCE2 Courses.

Read More


Closing a Project (CP) PROCESS

Written by Andy Trainer – Thu 12 Jul 2007

PRINCE2® PROCESSES – Closing a Project (CP)

See our courses for PRINCE2.

The purpose of the Closing a Project process is to provide a fixed point at which acceptance for the project product is confirmed, and to recognize that objectives set out in the original Project Initiation Documentation have been achieved (or approved changes to the objectives have been achieved), or that the project has nothing more to contribute.

The objective of the Closing a Project process is to:

  • Verify user acceptance of the project’s products
  • Ensure that the host site is able to support the products when the project is disbanded
  • Review the performance of the project against its baselines
  • Assess any benefits that have already been realized, update the forecast of the remaining benefits, and plan for a review of those unrealized benefits
  • Ensure that provision has been made to address all open issues and risks, with follow-on action recommendations.

The main products of this process are as follows:

  • Project Plan updated with final actual
  • Product Status Account covering the status of all products for the project
  • Issue register to identify any outstanding issues
  • Follow-on action recommendations created with any outstanding issues to be addressed
  • Configuration item records updated with current status of products
  • Benefits review plan updated with dates for benefits realization
  • Acceptance records for products completed
  • End project report created
  • Lessons Report created
  • Close Issue, Risk, Quality registers, Daily and Lessons Log

Read More