A project requires rapid CCB approval for a scope change. Which minimal set of elements should appear on the one-page executive impact package?

Concise description, reason/benefit, quantified cost/schedule/quality deltas, affected baselines

Concise description, quantified impacts, affected baselines, color-coded risk heat map

Full narrative description, stakeholder matrix, Gantt chart excerpt, risk register excerpt

Concise description, reason/benefit, quantified impacts, key stakeholder list

A stakeholder repeatedly bypasses the change control board and directly requests scope changes to the team. According to the project's escalation thresholds, what is the most appropriate sequence of actions?

Apply documented thresholds, notify the stakeholder of governance requirements, and document the interaction.

Escalate immediately to the steering committee without first applying the thresholds.

Accept the requests informally to preserve the relationship and avoid conflict.

Direct the team to implement changes only when impact exceeds 10 percent of budget.

A key stakeholder complains that the strict document control process is causing unacceptable delays and demands broad edit access to the active baseline repository to speed up minor revisions. What is the best course of action for the project manager?

Deny the request to protect baseline integrity while exploring new ways to safely streamline the formal review process

Approve the request for broad edit access but strictly require the stakeholder to verbally report implemented changes

Grant the stakeholder temporary edit access to the active repository until current project schedule pressure is relieved

Create a separate, unmonitored baseline repository for the stakeholder to make rapid changes without formal oversight

A major scope change is proposed during project execution. Before proceeding with the formal change control process, the project manager must evaluate the impact on the consolidated plan and forecasted benefit start dates. Which approach should the project manager take?

Use the integrated risk-and-procurement view to recommend adjustments that preserve continuing business value.

Submit the change request to the change control board with an updated critical path network analysis.

Immediately approve the requested scope change and update the comprehensive project management plan to reflect it.

Reject the change request outright because it jeopardizes the originally baselined cost and schedule constraints.

A late high-cost change request shows quantified schedule and cost impacts plus reduced expected benefit. Which decision best preserves stakeholder trust?

Negotiate scope reduction after impact analysis and re-approval

Reject the request and continue with the original baseline

Re-baseline immediately and notify stakeholders afterward

Escalate to the sponsor without presenting trade-off options

Three change requests link to requirements via the RTM. Which prioritization ranks them by stakeholder value and system impact?

Rank by combined stakeholder value score and quantified schedule-cost-risk impact.

Prioritize only by highest stakeholder value score.

Rank solely by lowest estimated implementation effort.

Approve all requests that affect fewer than three work packages.

A high-impact change request has exceeded the five-day change-board SLA. What is the most appropriate ordered response?

Acknowledge within SLA, prepare impact statement, escalate after timer if unresolved

Escalate immediately to the steering committee without stakeholder acknowledgement

Wait for full root-cause analysis before any notification

Ignore the breach because the issue appears minor to the team

After verification a stakeholder requests extra functionality. Which feedback represents a scope change rather than a defect?

Add encryption module not in original specifications

Measured output fails stated tolerance limits

Test script reveals unmet acceptance criterion

Component does not match approved design drawing

After a baseline update affecting operations, which communication elements must be included to meet audit requirements?

What changed, why, who is responsible, when effective, plus user impacts and handover needs.

Change description, effective date, training schedule, and risk register update.

Summary of the change request, updated schedule, and next status meeting date.

Description of the new baseline, affected deliverables, and revised budget figures.

After approving a rebaseline for a regulatory deliverable, which verification and validation actions must be completed before formal closure and acceptance?

Update test plans, acceptance criteria, and handover checklists to match the new baseline, then execute validation.

Archive prior baseline documents and obtain sponsor sign-off on the change request only.

Conduct stakeholder training on the new baseline and update the risk register.

Re-run the original test suite without revising acceptance criteria or handover checklists.

2.3.2

Domain 3 of 3 · Business Environment · task

Managing and controlling changes for the PMP® exam

Five beats make up change control in practice: log the request, analyze its impact, get a decision from whoever holds the authority, implement only what was approved, and update every document the change touches. The board meeting is one beat of five, and the other four are where changes tend to go wrong.

Exam: PMP
Domain: Business Env.
Domain weight: 26%
Packages: 15
Updated: Oct 13, 2026

Fig. 1 · chain

Change management as a flow. The decision is one box out of five.

01What the task covers beyond the board

The Business Environment task on managing and controlling changes lists executing the change control process, communicating the status of proposed changes, implementing approved changes and updating documentation (PMI® Examination Content Outline, paraphrased). The decision itself, who sits on a change control board (CCB) and what it weighs, is on integrated change control.

Communicating status is where real projects leak. A requester who hears nothing for three weeks starts asking the developers directly. Once a decision is made, the requester, the team and anyone whose work moves need to hear it, including when the answer is no.

Adaptive teams run the same five beats with different owners; the decision on new scope usually belongs to the product owner. On either kind of project, the baselines and backlog being protected were set during planning and scope.

One task out of eight in a domain PMI weights at 26% (as of October 2026): by our even-split estimate, about 3.3% of the exam.

02One approved change, many documents

What moves after a hypothetical approved change: adding a second distribution center to a warehouse-system rollout

Document	What changes
Scope statement and WBS	A new deliverable for the second site, with its work packages and dictionary entries
Schedule baseline	Cutover activities for site two and their dependencies on site one
Cost baseline	The approved budget for the added work
Risk register	New risks, such as two cutovers scheduled too close together, each with an owner
Stakeholder and communication plans	The site-two manager and staff, with the reports they will receive
Change log	Status set to approved, then implemented, with dates

WBS stands for work breakdown structure. A change that shows up in only one of these rows was probably not fully implemented.

03Change requests to work through

Where in the five beats does each scenario start?

Work packages 15

WP 01A project requires rapid CCB approval for a scope change. Which minimal set of elements should appear on the one-page executive impact package?
Debrief answer to open the notes
1. AA heat map is useful, but without the reason and benefit the board cannot weigh the change against its impact.
2. BFull narratives and excerpts make the package long, which defeats a one-page summary built for a quick decision.
3. CWithout the affected baselines and quality deltas, the board cannot see what approval would actually change.
4. DCorrect: the board needs what the change is, why it is worth doing, its quantified cost, schedule, and quality effects, and which baselines it touches.
More notes below ↓
WP 02A stakeholder repeatedly bypasses the change control board and directly requests scope changes to the team. According to the project's escalation thresholds, what is the most appropriate sequence of actions?
Debrief answer to open the notes
1. AEscalating before applying the agreed thresholds skips the process the project already defined.
2. BCorrect: apply the documented thresholds, remind the stakeholder that changes go through governance, and record the interaction for traceability.
3. CAccepting requests informally creates uncontrolled scope change and undermines the change board.
4. DHaving the team implement changes on its own above a cost limit bypasses the board entirely.
More notes below ↓
WP 03A key stakeholder complains that the strict document control process is causing unacceptable delays and demands broad edit access to the active baseline repository to speed up minor revisions. What is the best course of action for the project manager?
Debrief answer to open the notes
1. AEdit rights with verbal reporting break configuration control; nobody can later tell which version was approved.
2. BTemporary access is still uncontrolled access to the baseline, and schedule pressure is exactly when mistakes get made.
3. CAn unmonitored copy creates a second, conflicting version of the baseline.
4. DCorrect: baseline integrity stays protected, and the stakeholder's real complaint, slow reviews, is addressed by improving the process.
More notes below ↓
WP 04A major scope change is proposed during project execution. Before proceeding with the formal change control process, the project manager must evaluate the impact on the consolidated plan and forecasted benefit start dates. Which approach should the project manager take?
Debrief answer to open the notes
1. ASubmitting with a critical path analysis alone skips the benefit and procurement impacts the stem asks the project manager to weigh first.
2. BCorrect: the integrated view shows how the change ripples through risk and procurement, so the recommendation protects the business value the project exists to deliver.
3. CApproving immediately skips impact analysis and bypasses integrated change control.
4. DRejecting outright puts the original baselines ahead of value without analyzing the change at all.
More notes below ↓
WP 05A late high-cost change request shows quantified schedule and cost impacts plus reduced expected benefit. Which decision best preserves stakeholder trust?
Debrief answer to open the notes
1. ACorrect: after impact analysis, offering a scope trade-off and seeking re-approval keeps the decision transparent and protects value.
2. BRejecting without discussing options can damage trust when a negotiated version might still deliver value.
3. CRe-baselining before notifying stakeholders reverses the order and erodes trust.
4. DEscalating without options hands the sponsor a problem rather than a decision.
More notes below ↓
WP 06Three change requests link to requirements via the RTM. Which prioritization ranks them by stakeholder value and system impact?
Debrief answer to open the notes
1. AValue alone ignores the schedule, cost, and risk impact that the RTM links reveal.
2. BLowest effort favors easy changes regardless of value or impact.
3. CCorrect: combining stakeholder value with quantified impact ranks the changes on both dimensions the RTM supports.
4. DA work-package count says nothing about value and is an arbitrary approval rule.
More notes below ↓
WP 07A high-impact change request has exceeded the five-day change-board SLA. What is the most appropriate ordered response?
Debrief answer to open the notes
1. AEscalating without acknowledging the requester leaves them uninformed and skips a step the SLA expects.
2. BCorrect: acknowledge first, prepare the impact statement, and escalate only when the timer expires unresolved, which keeps the response orderly and proportionate.
3. CWaiting for full root cause extends the breach and leaves the requester without an answer.
4. DIgnoring a breach of a high-impact request undermines the change process.
More notes below ↓
WP 08After verification a stakeholder requests extra functionality. Which feedback represents a scope change rather than a defect?
Debrief answer to open the notes
1. AOutput outside the stated tolerance is a defect against existing requirements.
2. BAn unmet acceptance criterion is a defect, because the criterion was already part of scope.
3. CCorrect: an encryption module that was never specified adds new functionality, so it is a scope change that needs change control.
4. DNot matching the approved design is nonconformance, which makes it a defect.
More notes below ↓
WP 09After a baseline update affecting operations, which communication elements must be included to meet audit requirements?
Debrief answer to open the notes
1. ACorrect: audit-ready communication covers what changed, why, who owns it, and when it takes effect, plus user impacts and handover needs for operations.
2. BTraining dates and a register update help, but the rationale and the owner are missing.
3. CA summary and next meeting date omit why the change happened and who is responsible.
4. DBudget figures and deliverables describe the new baseline but leave out why, who owns it, and when it takes effect.
More notes below ↓
WP 10After approving a rebaseline for a regulatory deliverable, which verification and validation actions must be completed before formal closure and acceptance?
Debrief answer to open the notes
1. AArchiving and sponsor sign-off on the request do not show that the deliverable meets the new baseline.
2. BTraining and register updates are helpful but are not verification or validation.
3. CCorrect: test plans, acceptance criteria, and handover checklists must reflect the new baseline before validation can confirm the deliverable meets it.
4. DRe-running the original tests checks the old baseline, not the approved one.
More notes below ↓
WP 11An empowered cross-functional agile team decides to add several advanced features to a product increment. The product owner notices these additions deviate from the approved baseline and introduce severe scope creep, risking non-compliance with industry regulations. How should the project manager address this situation?
Debrief answer to open the notes
1. ACorrect: empowerment works within guardrails, so restating authority limits protects compliance while keeping the team self-organizing.
2. BLetting the team proceed ignores compliance risk and the approved baseline.
3. CRevoking empowerment overcorrects and slows the team on work that was never the problem.
4. DA change order for features the team added on its own treats the symptom, not the missing guardrails.
More notes below ↓
WP 12Stakeholders request new features mid-sprint. Which mini-process preserves sprint cadence while enabling formal evaluation?
Debrief answer to open the notes
1. ACorrect: the request is recorded and sized, the product owner decides at backlog review, the sprint goal stays protected, and regulatory effects go to formal control.
2. BAdding work mid-sprint disrupts the sprint goal the team committed to; new items go to the product owner first.
3. CBlanket rejection ignores requests that may be valuable and delays the product owner's decision for no reason.
4. DVerbal approval with paperwork later skips the impact check and leaves no record of the decision.
More notes below ↓
WP 13Three change requests conflict on scope, schedule, and cost. Which tradeoff log entry best resolves them while preserving governance?
Debrief answer to open the notes
1. AApproving everything and extending three weeks resolves no conflict and lacks documented rationale.
2. BAccepting only the delay and logging it as a risk ignores the scope and cost dimensions.
3. CRejecting all requests avoids trade-offs and may discard value.
4. DCorrect: it makes an explicit trade-off on each dimension and records the rationale and sign-offs, which is what a governed trade-off log needs.
More notes below ↓
WP 14Undocumented scope increases of $18,000 and two weeks have been discovered. Current BAC is $420,000 and EAC is $445,000. Which governance action and EAC recalculation is required?
Exhibit for WP 14
Change Item Added Budget ($) Added Duration (weeks)
New reporting module 12,000 1.5
Additional security review 6,000 0.5
Debrief answer to open the notes
1. ACorrect: unapproved scope must go through change control first; if approved, EAC = 445,000 + 18,000 = $463,000 and the baseline is updated.
2. BIgnoring known work leaves the forecast and baseline wrong and keeps unauthorized scope hidden.
3. CReporting it as a variance treats new scope as poor performance and skips the approval decision.
4. DThe $463,000 figure is right, but changing the forecast without change control legitimizes unapproved scope.
More notes below ↓
WP 15In a software development project, different issues have been reported during the testing phase. Based on the information, which is the most suitable change request type for each issue?
Exhibit for WP 15
Issue Change Type
Software crash identified due to a memory leak
Logs show potential risk of future downtime; requires system upgrade
Tasks diversion leading to delay; need to realign project deadlines
Debrief answer to open the notes
1. ADefect repair fixes a nonconforming product; a schedule slip from diverted tasks calls for corrective action instead.
2. BA crash from a memory leak is a product defect, so it needs defect repair, not corrective action.
3. CPreventive action targets future problems; the crash has already happened and needs defect repair.
4. DCorrect: the crash is a defect (defect repair), the downtime risk is future (preventive action), and the slip realigns work to plan (corrective action).
More notes below ↓

Change Item	Added Budget ($)	Added Duration (weeks)
New reporting module	12,000	1.5
Additional security review	6,000	0.5

Issue	Change Type
Software crash identified due to a memory leak
Logs show potential risk of future downtime; requires system upgrade
Tasks diversion leading to delay; need to realign project deadlines

Open a row to answer. Keys: 1–4 or A–D answer, N opens the next row.

04The change log and the risks a change brings

What goes into the change log?

Every request, approved or not: what was asked, by whom, the impact analysis, the decision, who made it and when, and whether an approved change has been implemented. It is the record an auditor or a new team member reads to understand why the plan looks the way it does.

Can an approved change create new risks?

Often. A schedule squeezed to fit new scope, or a new supplier, brings threats of its own, and they go into the register with owners. The handling of those is on risks, issues and impediments.