Change Control is a fundamental aspect of the Issues practice in PRINCE2 7, providing a systematic approach to managing modifications to project baselines. It ensures that all changes are properly evaluated, authorized, and implemented in a controlled manner, protecting the project from uncontrolle…Change Control is a fundamental aspect of the Issues practice in PRINCE2 7, providing a systematic approach to managing modifications to project baselines. It ensures that all changes are properly evaluated, authorized, and implemented in a controlled manner, protecting the project from uncontrolled scope creep and maintaining product integrity.
The Change Control process begins when a change request is raised, typically through a Request for Change (RFC). This formal document captures the details of the proposed modification, including its rationale, impact assessment, and potential benefits. All change requests must be logged in the Issues Register for tracking and management purposes.
Once a change request is submitted, it undergoes a thorough impact analysis. This assessment examines how the proposed change affects the project's time, cost, quality, scope, benefits, and risks. The analysis provides decision-makers with the information needed to make informed choices about whether to approve, reject, or defer the change.
The Project Board typically holds the authority to approve significant changes, though they may delegate minor change decisions to the Project Manager through defined tolerances or a Change Authority. The Change Authority concept allows for more efficient handling of changes by empowering designated individuals or groups to make decisions within specified parameters.
PRINCE2 7 emphasizes maintaining a Change Budget, which is a sum of money set aside to fund approved changes. This approach prevents projects from constantly returning to corporate management for additional funding for minor modifications.
Effective Change Control maintains traceability throughout the project lifecycle, ensuring that all decisions are documented and that the impact of approved changes is reflected in updated plans and baselines. This practice supports good governance by providing transparency and accountability in how project modifications are handled, ultimately contributing to successful project delivery.
Change Control in PRINCE2 Foundation v7 - Complete Guide
What is Change Control?
Change Control is a procedure within the Issues practice that ensures all proposed changes to the project's baseline products are properly assessed, authorised, and managed. It provides a systematic approach to handling requests for modifications to agreed deliverables, scope, or other aspects of the project.
Why is Change Control Important?
Change Control is essential for several key reasons:
• Protects baseline integrity: It ensures that approved products and plans are not altered arbitrarily • Maintains project control: All changes are assessed for their impact on time, cost, quality, scope, benefits, and risk • Ensures proper authorisation: Changes are approved by the appropriate authority before implementation • Provides traceability: A clear audit trail exists for all changes made during the project • Manages stakeholder expectations: Everyone understands what has been agreed and what has changed
How Change Control Works
The change control procedure follows a structured approach:
1. Capture: A request for change is raised and logged in the Issue Register
2. Examine: The impact of the proposed change is analysed, considering effects on the project's six performance targets (time, cost, quality, scope, benefits, risk)
3. Propose: Options are identified and recommendations made to the appropriate decision-maker
4. Decide: The change authority determines whether to approve, reject, or defer the change
5. Implement: If approved, the change is incorporated into the relevant products and plans
Key Concepts to Remember
• Change Authority: The person or group authorised to approve changes within defined limits. This could be the Project Board, Project Manager, or a separate Change Authority depending on the change budget allocated
• Change Budget: Money or time set aside to fund approved changes. The Project Board decides how much authority to delegate
• Configuration Management: Works closely with change control to track product versions and their status
• Baseline: The reference point against which changes are assessed
Types of Issues Related to Change
• Request for Change: A proposal to modify a baseline product • Off-specification: A product that does not meet its specification (may require a change to resolve) • Problem/concern: Any other issue that needs resolution
Exam Tips: Answering Questions on Change Control
Tip 1: Remember that change control applies to baselined products - products that have been approved and are under configuration management
Tip 2: Know the difference between a Request for Change (proactive proposal for modification) and an Off-specification (reactive response to something not meeting requirements)
Tip 3: Understand the role of the Change Authority - they can be the Project Board, a delegated group, or the Project Manager for minor changes
Tip 4: Focus on impact assessment - questions often test whether you understand that changes must be evaluated against all performance targets
Tip 5: Remember the Issue Register is where all issues (including change requests) are recorded and tracked
Tip 6: The Project Board sets the change budget and decides how much authority to delegate for approving changes
Tip 7: If a question mentions someone wanting to alter an approved product, think change control procedure
Tip 8: Configuration management and change control work together - changes to products require updates to configuration records