Study guide
15.2 Managing Scope Through Configuration Management
APM Project Management Qualification PMQ
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Exam Format & Question Types 1.3 How to Study for APM PMQ
2 Life Cycles
2.1 Linear Life Cycles and Why Work Is Phased 2.2 Iterative and Hybrid Life Cycles 2.3 Project Life Cycles and Extended Life Cycles 2.4 Choosing a Life Cycle: Context, Culture, Strengths and Limitations
3 Governance Arrangements
3.1 Functional, Matrix and Projectised Structures 3.2 Governance Frameworks, Policies and Delegated Responsibility 3.3 Life-Cycle Impact on Governance and Limits of Financial Authority 3.4 Project Roles and Responsibilities 3.5 Project Manager and Project Sponsor Through the Life Cycle 3.6 Linking Projects to Organisational Objectives
4 Sustainability
4.1 Sustainability Responsibilities, Principles and Impact 4.2 Monitoring and Reporting Sustainability Measures
5 Business Case
5.1 Business Case Fundamentals and Analysis Tools 5.2 The Business Case as Baseline and Reviewing Change
6 Procurement
6.1 Procurement Strategy: Purpose and Contents 6.2 Supplier Selection and Negotiation 6.3 Features of Different Contractual Relationships 6.4 Supplier Reimbursement Methods
7 Reviews & Assurance
7.1 Reviews, Decision Gates, Benefits Reviews and Audits 7.2 What Gets Reported and Informing Decisions 7.3 Why Activities Are Re-Planned After a Review 7.4 Project Assurance
8 Transition & Benefits Management
8.1 Transition Requirements and Business-as-Usual Readiness 8.2 Knowledge Transfer and Agreeing the Transition Plan 8.3 Benefits Management: Identification to Realisation 8.4 Aligning and Communicating Benefits
9 Stakeholder Engagement & Communication
9.1 Stakeholder Analysis, Influence and Engagement 9.2 The Communication Management Plan and Its Benefits 9.3 Managing Stakeholder Expectations 9.4 Communication Methods and Tailoring the Message 9.5 Factors That Help and Hinder Communication
10 Conflict Resolution
10.1 Sources and Impacts of Conflict 10.2 Addressing Conflict and the Thomas-Kilmann Model
11 Leadership
11.1 Leadership, Motivation and Team Performance 11.2 Changing Leadership Styles for the Situation 11.3 Coaching, Mentoring and Emotional Intelligence
12 Team Management
12.1 Team Development Stages and Models 12.2 Characteristics and Benefits of Effective Teams 12.3 Leading Virtual and Hybrid Teams
13 Diversity & Inclusion
13.1 Diversity Characteristics and the Equality Act 13.2 Incorporating Diversity and Diverse Thinking 13.3 Conscious and Unconscious Bias and Fair Treatment
14 Ethics, Compliance & Professionalism
14.1 Continuing Professional Development and Competence 14.2 Sources of Specialist Advice and Standards 14.3 The Legal and Regulatory Landscape
15 Requirements & Solutions
15.1 Establishing Scope Through Requirements Management 15.2 Managing Scope Through Configuration Management 15.3 Solutions Development and Prioritisation
16 Quality Management
16.1 Quality Planning, Indicators and the Business Case 16.2 Quality Control and Success Criteria
17 Integrated Planning
17.1 The Integrated Project Management Plan: Format and Contents 17.2 Why an Integrated Plan Matters
18 Schedule Management
18.1 Defining Scope and Breakdown Structures 18.2 Dependencies and What Drives the Schedule 18.3 Re-Estimating and Schedule Optimisation
19 Resource Management
19.1 Determining Resource Requirements and Availability 19.2 Organisational Breakdown Structure and RACI 19.3 Categorising and Allocating Resources 19.4 Resource Smoothing and Resource Levelling
20 Budgeting & Cost Control
20.1 Creating a Budget and Cost Types 20.2 Earned Value and Cost Forecasting 20.3 Monitoring and Reporting Financial Performance 20.4 Closing Down Project Finances
21 Risk & Issue Management
21.1 Benefits of Risk and Issue Management and Contingency Planning 21.2 The Risk and Issue Management Processes 21.3 Proactive and Reactive Risk Responses 21.4 Governance in Risk and Issue Management
22 Change Control
22.1 The Change Control Process and Its Stages 22.2 What a Change Request Must Capture 22.3 Assessing Options and the Impact of a Change 22.4 Recommending Decisions and Updating Plans
Free exam prep APM Project Management Qualification (PMQ) Practice Questions 135 questions Study Guide 74 topics
15.2 Managing Scope Through Configuration Management
Key Takeaways Explain This Topic AI
The five configuration management activities are planning, identification, control, status accounting, and verification audit.
Identification assigns unique references and versions so everyone can say exactly which item and which version they mean.
Control ensures changes to configuration items happen only through the agreed process, protecting the integrity of the baseline.
Status accounting records the current state and history of every configuration item, which is what makes reporting and audit possible.
Verification audit confirms the physical reality matches the records, catching undocumented changes before they reach handover. Last updated: August 2026
Outcome 16b names five configuration management activities explicitly: planning, identification, control, status accounting and verification audit . Named process steps in a syllabus are near-certain exam content, so learn what each one does and what fails without it. Managing scope through configuration management Configuration management (CM) is the discipline that ensures the products, components, and documentation of the project remain identified, consistent, and controlled as they evolve. If requirements management defines the needed scope, CM protects the integrity of the evolving solution and its records so that teams build, test, and hand over the correct configuration. Scope creep often appears as uncontrolled document or product versions: two drawings, three requirement lists, and a "final_final_v7" build that nobody can relate to approved tests. CM prevents that chaos. The five configuration management processes APM-aligned teaching commonly recognises five CM processes. Learn them as a complete system, not isolated jargon.
Process Purpose Typical activities Failure if weak 1. Configuration management planning Define how CM will work on this project CM plan: items in scope, naming/version rules, tools, roles, baselining points, audit approach, link to change control Ad hoc versioning; inconsistent team habits 2. Configuration identification Decide what will be controlled and how it is uniquely labelled Select configuration items (CIs); assign IDs; define product breakdown/structure; specify baselining events Unclear what is "the product"; cannot find the approved item 3. Configuration control Manage changes to baselined CIs Raise change requests; impact assess; approve/reject; update items and related docs; release new versions Unauthorised changes; silent scope growth 4. Configuration status accounting Record and report the status of CIs and changes Status records, version histories, change logs, progress of approved changes Nobody knows current approved state or open changes 5. Configuration verification and audit Confirm physical/actual items match approved records Reviews, configuration audits, reconciliations before gates/handover "As-built" differs from "as-documented"; failed assurance 1. Configuration management planning Planning sets the rules before complexity explodes. A configuration management plan (standalone or embedded in the PMP) typically covers: Which products and documents are configuration items Naming, numbering, and version conventions Tools (registers, repositories, PLM/ALM tools) Roles (configuration librarian/manager, change authority) When baselines are created (requirements, design, product, handover) How CM links to change control, quality, and release management Audit schedule and gate evidence expectations Planning is proportionate: a small internal process change needs lighter CM than a multi-contractor infrastructure asset with safety-critical drawings. 2. Configuration identification Identification answers: what are the configuration items, and how is each uniquely known? Configuration items (CIs) might include requirement specifications, design models, software builds, hardware assemblies, test procedures, training materials, or as-built drawings — selected by risk and need for control. Over-controlling every email is wasteful; under-controlling critical products is dangerous. Identification also defines the product structure (how parts relate) so impact analysis can see that changing Module A affects Interface B and Test Pack C. 3. Configuration control Control is the operational heart of CM. Once a CI is baselined, changes follow a controlled path: Propose change with rationale Assess impact on scope, time, cost, quality, risk, benefits, and related CIs Decide via agreed authority (project manager, change board, sponsor — per governance) Implement approved changes and update all related configuration information Release the new approved version and withdraw superseded items from use Configuration control and project change control are tightly linked: change control decides whether the project should accept a change; configuration control ensures the product and document set actually reflects the decision. 4. Configuration status accounting Status accounting is the information service of CM. It answers questions such as: What is the current approved version of CI-017? Which changes are proposed, approved, implemented, or rejected? Which baseline was used for the last test run? What is the configuration of the build going to pilot users? Without status accounting, control decisions cannot be evidenced and teams work from stale copies. 5. Configuration verification and audit Verification and audit check that reality matches the record. A configuration audit may confirm that the installed asset, software release, or document pack matches the approved configuration baseline and that mandatory changes have been incorporated. This is especially critical before handover/transition , major gates, or regulated go-live.
Audit focus Example question Functional Does the item meet the baselined requirements/performance? Physical / configuration Does the as-built item match drawings, BOMs, and version records? Scenario B — configuration failure at handover A manufacturing line upgrade is "complete," but operations receive training manuals for software build 3.2 while the live PLC runs build 3.4 with two unrecorded parameter changes made overnight by a contractor. Status accounting and verification audit were skipped. Result: incidents, blame, and delayed benefits. Correct practice: identify critical CIs, control parameter changes, maintain status records, and audit configuration before acceptance. Linking requirements baselining to scope control Think of the chain as: Gathered needs → analysed & justified requirements → requirements baseline → design/product baselines (CIs) → configuration control of changes → status accounting & audit evidence Scope is therefore managed by: Defining scope through justified requirements Baselining those requirements (and related product definitions) Forcing subsequent change through impact assessment and authority Keeping configuration records consistent with decisions Verifying that delivered products match approved configuration Scenario C — "small tweak" that was not small A stakeholder asks the developer to "just add one extra report" outside the change process. That report needs new data feeds, security roles, and test cases — a multi-CI impact. Without configuration control, the team absorbs silent scope, misses tests, and fails UAT. The PM should route the request through change/configuration control, re-baseline if approved, and replan tests and training. Answer pattern for LO16 long responses When a scenario shows unclear scope, conflicting asks, or version chaos: Separate requirements management (establish what is needed) from configuration management (control what is produced and recorded). Walk gather → analyse → justify → baseline for establishing scope. Name all five CM processes where relevant, with purpose not only labels. Link baselines to change control and governance authority. Use a scenario example (wrong version, gold-plating, silent tweak) to show applied judgement. That structure scores as professional scope control rather than a generic "manage stakeholders better" answer.
Test Your Knowledge
What is the primary purpose of configuration status accounting?
A
To invent new requirements without sponsor approval
B
To record and report the current versions, baselines, and change status of configuration items so the team knows the approved state
C
To replace the need for quality control or testing
D
To delete historical versions so only one informal copy exists Check Answer Need a hint? AI
Test Your Knowledge
A contractor changes a baselined design drawing on site without going through the agreed process. Which configuration management response is most appropriate?
A
Ignore the change if the contractor is experienced
B
Treat it as controlled only if it reduces cost, regardless of impact
C
Raise and assess the change under configuration control, update related configuration items and records if approved, and verify the as-built state matches approved records
D
Wait until final handover and hope operations notice differences Check Answer Need a hint? AI
Sections you finish are checked off in the contents.
Up Next 15.3 Solutions Development and Prioritisation Continue learning
Independent exam preparation notice OpenExamPrep is an independent education provider, not affiliated with or endorsed by the exam sponsors named on this site. Exam and certification names identify what our resources help you study for; they do not imply sponsorship, approval, or review of our materials. Unless a resource expressly identifies authorized public material, our practice questions are independently developed simulations, not actual, recalled, or sponsor-provided exam items. We aim to reflect publicly available exam outlines and topic information in our study resources. Coverage, format, and difficulty may differ from the actual exam, and we cannot guarantee that every detail is accurate or current. Confirm exam requirements, fees, and policies with the official exam sponsor.