Change

• Purpose
• Change defined
  • Issue and change control
  • Configuration management
  • Issues
  • Types of issue
• Establish controls
  • Overview
  • Configuration Management Strategy
  • Configuration Item Records
  • Product Status Account
  • Daily Log
  • Issue Register
  • Issue Report
• Configuration management procedure
• Issue and change control procedure
  • Overview
  • Capture
  • Examine
  • Propose
  • Decide
  • Implement
• Responsibilities

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

The PRINCE2® approach

Issue and change control procedure

© Crown copyright 2005 Reproduced under licence from OGC

Propose

Having gained a full understanding of the impact of the issue, the next step is to consider alternative options for responding to it and proposing a course of action to take.

Consideration should be given as to the effect each of the options will have on the project’s time, cost, quality, scope, benefit and risk performance targets. There must be a balance between the advantage to be gained by implementing the option, and the time, cost and risk of implementing it, as shown in the diagram.

The risk considerations should include both project risks (i.e. of not completing within tolerances) and operational risks (e.g. potential performance issues once the project’s products are in use).

If any of the proposed options would take the stage or project beyond any tolerances, consider preparing an Exception Report for that option to accompany the Issue Report.

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