Study guide
5.3 Change Control & Configuration Management
PRINCE2 7 Foundation Certification Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Key Concepts, Framework & Integrated Elements
1.1 PRINCE2 7 Method Overview & Project Context 1.2 Seven Performance Aspects & Delivery Approaches 1.3 Outputs, Outcomes, Benefits & Value Creation 1.4 Management Products vs Specialist Products 1.5 PRINCE2 Governance, Tailoring & Distinct Features
2 Chapter 2: The Seven PRINCE2 7 Principles
2.1 Principle 1: Continued Business Justification 2.2 Principle 2: Learn from Experience 2.3 Principle 3: Define Roles, Responsibilities and Relationships 2.4 Principle 4: Manage by Stages 2.5 Principle 5: Manage by Exception 2.6 Principle 6: Focus on Products 2.7 Principle 7: Tailor to Suit the Project
3 Chapter 3: The People Element in PRINCE2 7
3.1 Capable People & Organizational Culture 3.2 Project Teams & Team Dynamics 3.3 Leading Project Teams 3.4 Communication & Stakeholder Engagement 3.5 Organizational Change Management (OCM)
4 Chapter 4: The PRINCE2 7 Practices - Strategy, Organization & Planning
4.1 Business Case Practice 4.2 Organizing Practice & Project Management Team 4.3 Commercial & Stakeholder Aspects of Organizing 4.4 Plans Practice & Levels of Plans 4.5 Product-Based Planning Technique 4.6 Quality Practice & Quality Control
5 Chapter 5: The PRINCE2 7 Practices - Risk, Change & Progress Control
5.1 Risk Practice & Risk Management Approach 5.2 Issues Practice & Issue Management Approach 5.3 Change Control & Configuration Management 5.4 Progress Practice & Control Mechanisms 5.5 Management Reports & Logs/Registers 5.6 Sustainability & Digital Integration in Practices
6 Chapter 6: The PRINCE2 7 Processes - Pre-Project & Initiation
6.1 Overview of PRINCE2 7 Process Model & Flow 6.2 Starting Up a Project (SU) Process 6.3 Directing a Project (DP) Process 6.4 Initiating a Project (IP) Process 6.5 Assembling the Project Initiation Documentation (PID)
7 Chapter 7: The PRINCE2 7 Processes - Delivery, Boundary & Closure
7.1 Controlling a Stage (CS) Process 7.2 Managing Product Delivery (MP) Process 7.3 Managing a Stage Boundary (SB) Process 7.4 Closing a Project (CP) Process 7.5 End-to-End PRINCE2 7 Process Flow & Exam Walkthrough
5.3 Change Control & Configuration Management
Key Takeaways Explain This Topic AI
Configuration Management provides the discipline for identifying, tracking, safeguarding, and auditing project deliverables and management products.
A Baseline is an approved version of a product or management document that can only be modified through formal change control.
Configuration Item Records (CIRs) maintain the detailed history, status, version number, location, and relationships for every tracked product.
The Product Status Account is a report summarizing the current status and version history of configuration items across the project or stage.
Modern digital change control integrates PRINCE2 baselining with version control systems (e.g., Git), automated CI/CD pipelines, and feature toggles.
Last updated: July 2026
5.3 Change Control & Configuration Management
Change control cannot operate effectively without Configuration Management . While issue management provides the decision-making process for evaluating change, configuration management provides the underlying technical control that identifies, tracks, and safeguards products, ensuring that project teams always know which version of a deliverable is approved.
PRINCE2 7 Principle: Change control and configuration management go hand in hand. If you do not control product baselines, you cannot control change.
What is Configuration Management?
Configuration Management is the management practice responsible for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its lifecycle.
In PRINCE2 7, every deliverable (specialist product) and management artifact (management product) that requires version control is designated as a Configuration Item (CI) .
The Four Core Functions of Configuration Management
Identification: Specifying products, assigning unique naming structures, defining product breakdown structures, and establishing version numbering schemes (e.g., Major.Minor.Patch format).
Control: Ensuring products are frozen and baselined upon formal sign-off, and enforcing that modifications occur exclusively via approved Requests for Change.
Status Accounting: Maintaining live records and generating reports on the location, state, author, owner, and version history of configuration items throughout the project.
Verification & Audit: Conducting systematic physical and functional reviews to confirm that physical assets or digital code matches the specifications documented in Configuration Item Records.
The Concept of Baselining
A Baseline is a cornerstone concept in PRINCE2 progress and change control.
PRINCE2 7 Definition: A Baseline is an approved version of a product or management document that can only be changed through formal change control procedures.
The Baselining Lifecycle Step-by-Step
Draft Development (v0.1, v0.2...): Products are created and iteratively refined by technical teams or project authors. Edits occur freely without formal change board review.
Quality Review & Baseline Sign-Off (v1.0): Once a product satisfies its Product Description quality criteria, it is formally signed off by designated reviewers and baselined (frozen).
Proposed Change (v1.1 draft): If a stakeholder submits a Request for Change (RFC) and it is approved by the Change Authority, a new working version is checked out.
Re-baselining (v2.0): Following implementation, testing, and quality verification of the change, the updated version is formally re-baselined as version 2.0. [Draft Work: v0.1] ──> [Quality Review] ──> [BASELINED: v1.0] ──> [RFC Approved] ──> [Draft: v1.1] ──> [RE-BASELINED: v2.0]
Key Configuration Records & Management Products
PRINCE2 defines three primary management products to support configuration management:
1. Configuration Management Approach
Formulated during project initiation, this document specifies how configuration management will be executed, defining:
Naming conventions, repository structures, and versioning schemes.
Storage locations, cloud repository security, and role-based access rights.
Roles responsible for configuration management (e.g., Configuration Librarian / Project Support).
Audit schedules, verification criteria, and baselining procedures.
2. Configuration Item Record (CIR)
PRINCE2 7 Definition: A record that provides a detailed description of the status, version, location, relationships, and history of a specific Configuration Item.
For every tracked product, a CIR is maintained in the project's configuration management database (or digital tool). Key CIR fields include:
Item Identifier & Name: Unique reference ID (e.g., CI-MODULE-PAYMENT-004).
Current Version & Status: (e.g., In Development, Under Test, Baselined, Archived).
Location / Repository Path: Digital URI or physical storage coordinates.
Product Owner & Author: Designated technical leads and owners.
Variant / Branch Information: Environment branch details (e.g., staging vs production).
Relationships & Dependencies: Downstream components dependent on this item.
History of Changes: Audit trail of previous baseline modifications and linked RFC IDs.
3. Product Status Account
PRINCE2 7 Definition: A report issued by Project Support summarizing the status of configuration items within a stage, release, or the entire project.
The Product Status Account answers critical management questions such as: "Which products scheduled for Stage 2 delivery have reached baselined status?" or "What outstanding Requests for Change currently impact Component B?"
Management Product Primary Purpose Key Contents Target Audience
Configuration Management Approach Defines procedures & rules Naming schemes, tools, audit schedules, access rules Project Team & Quality Assurance
Configuration Item Record (CIR) Tracks individual product metadata Status, version history, location, dependencies Project Support & Technical Leads
Product Status Account Summarizes project-wide status Baseline state of all products in stage or release Project Manager & Project Board
Configuration Audits & Verification
Periodically, Project Assurance or an independent auditor conducts a Configuration Audit to verify that recorded records reflect physical reality:
Physical Audit: Checks that the physical assets, hardware items, or digital files listed in the Configuration Item Records actually exist in designated storage locations.
Functional Audit: Checks that the configuration items perform correctly and satisfy their specified requirements, security criteria, and operational standards as documented in their Product Descriptions.
Digital Integration & Agile Change Control
In modern PRINCE2 7 implementations, manual configuration logs are replaced by automated digital systems:
Git Version Control: Commits, feature branches, and pull requests automatically update Configuration Item Records.
Automated CI/CD Pipelines: Build pipelines automatically enforce quality checks, run unit tests, and freeze baseline releases upon successful build completion.
Feature Toggles / Flags: Enable digital teams to deploy baselined code to production while dynamically enabling or disabling features without breaking baseline integrity.
Digital Dashboards: Generate Product Status Accounts on demand directly from software repositories (e.g., Jira, GitHub, Azure DevOps).