Change Control, Issues and Impediments
PMP PMP · Business Environment
Change is certain; uncontrolled change is the problem
Every project changes. Requirements evolve, stakeholders change their minds, regulations shift, and new information emerges. The July 2026 ECO gives the Business Environment domain two tasks here: manage and control changes, and remove impediments and manage issues. Both moved into Business Environment from Process in the 2026 ECO, which reflects PMI's view that change and issue management are business disciplines — they protect the project's value and its alignment with organizational goals, not just its schedule and budget. The exam tests change control as a formal process with a clear sequence, and it tests issue and impediment management as a servant-leadership responsibility: the project manager removes obstacles so the team can deliver.
Integrated change control is the process of reviewing all change requests, approving or rejecting them, and managing changes to the deliverables, the project documents, and the project management plan. "Integrated" means the same thing here as in integrated planning: every change is assessed for its impact across the whole project — scope, schedule, cost, quality, risk, resources, and stakeholders — before a decision is made. A change that looks small in one dimension can be large in another: adding a feature may cost little in development time but require extensive new testing, training, and documentation. The exam tests this integrated assessment constantly, and the correct answer is almost always the option that assesses the full impact before deciding.
The change control process step by step
The change control process follows a fixed sequence that the exam tests directly:
| Step | What happens |
|---|---|
| 1. Submit the change request | Anyone (stakeholder, team member, customer) can submit a change request, describing the proposed change and why it is needed. Requests are documented — verbal requests are not processed. |
| 2. Assess the impact | The project manager (with the team) evaluates the effect on scope, schedule, cost, quality, risk, and resources. |
| 3. Decide | The change control board (CCB) — or the person with the authority defined in the change management plan — approves, rejects, or defers the change. |
| 4. Update the plan and baselines | If approved, the project management plan, baselines, and project documents are updated to reflect the change. |
| 5. Communicate | All affected stakeholders are informed of the decision and its consequences. |
| 6. Implement and verify | The change is implemented, and the results are verified against the updated plan. |
The most common exam trap is skipping a step: implementing a change before it is approved, or approving a change before its impact is assessed. A question describing a stakeholder who asks for a change and a project manager who immediately tells the team to build it is describing a failure of change control, no matter how reasonable the change seems. Another trap is the project manager making a change decision that belongs to the CCB: the project manager assesses and recommends, but the CCB (or the authorized decision-maker) decides — unless the change management plan gives the project manager authority over changes below a certain threshold.
Change in agile and hybrid projects
In agile projects, change is handled differently but not less rigorously. Instead of a formal change control board, changes are managed through the product backlog: new requirements and changes are added to the backlog, prioritized by the product owner against existing work, and pulled into future iterations. The key principle is the same — changes are assessed and prioritized before they are worked on — but the mechanism is lighter and faster. The exam tests this through scenarios: a stakeholder who asks for a change mid-sprint should be directed to the product owner, who adds it to the backlog for prioritization; the team does not abandon the current sprint to work on it. The sprint scope is protected during the sprint, and changes wait for the next planning event unless they are genuinely urgent.
In hybrid projects, the two approaches are combined: the overall project may use formal change control for scope and budget changes, while the agile delivery teams manage detailed changes through their backlogs. The project manager's job is to make sure the two mechanisms connect — that a backlog change with a significant impact on the overall project is escalated to formal change control.
Issues: problems that have already happened
An issue is a problem that has already occurred (or is currently occurring) and needs to be resolved — as opposed to a risk, which is a future uncertainty. Issues are recorded in the issue log, which tracks the issue, its owner, its priority, its status, and its resolution. The exam tests the risk/issue distinction directly: a question describing an event that has already happened and asking for the risk response is a trap — the correct answer is to manage it as an issue. Issue management follows the same PMI pattern as everything else: understand the issue, assess its impact, assign an owner, resolve it at the lowest possible level, and escalate only if it cannot be resolved there.
Common project issues include resource conflicts, technical problems, stakeholder disagreements, and vendor failures. The project manager's role is to ensure issues are logged, owned, and resolved — not to solve every issue personally. Delegating issue resolution to the person best placed to solve it, while tracking progress, is the servant-leader approach. The exam also tests the issue log as a communication tool: stakeholders should be able to see what issues are open, who owns them, and what is being done — transparency about problems builds trust, while hiding them destroys it.
Impediments: removing what blocks the team
An impediment is anything that blocks the team from doing its work: a missing decision, an unavailable resource, a broken tool, an organizational policy, a dependency on another team. In agile environments, removing impediments is one of the project manager's (or Scrum Master's) primary responsibilities. The exam tests this through scenarios where the team is blocked: the correct answer is always some version of "remove the impediment" — escalate the missing decision, secure the resource, fix the tool, negotiate the dependency. What the project manager does not do is tell the team to work around the impediment indefinitely, or to wait passively for it to resolve itself.
Impediment removal is where servant leadership is most visible. The project manager acts as a shield and a facilitator: they take on the organizational work — chasing approvals, resolving dependencies, clearing bureaucratic obstacles — so the team can focus on delivering. A question describing a team waiting for a decision from a busy executive is testing whether the project manager would chase the decision themselves rather than leaving the team blocked. The answer is always to act: the project manager's job is to make the team's path clear.
Exam mindset for change, issues, and impediments
For change questions, the pattern is: document the request, assess the full impact, get the decision from the authorized body, update the plan, communicate, and then implement. Never skip a step, and never implement before approval. For issue questions, the pattern is: log it, own it, resolve it at the lowest level, escalate only if necessary. For impediment questions, the pattern is: remove it. The project manager exists to clear the team's path, and the exam rewards the project manager who acts on obstacles rather than working around them.
Exam traps to watch for
- Implementing a change before it is approved. No matter how reasonable the change, work starts only after formal approval.
- Treating an event that has already happened as a risk. It is an issue now, managed through the issue log — not a risk response.
- Letting the team work around an impediment indefinitely. The project manager's job is to remove impediments, not to accept them.
- Allowing mid-sprint scope changes in agile projects. Changes go to the product owner and the backlog; the sprint scope is protected.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A stakeholder asks the project manager to add a new report to the project. The project manager estimates the report will take one week to build. What should the project manager do NEXT?
Explanation: Every change — even a small one — goes through integrated change control: the request is documented, its full impact is assessed (one week of building may also mean testing, documentation, training, and maintenance), and it is approved by the authorized decision-maker before work begins. Option B is wrong because implementing before approval is scope creep, regardless of the size of the change. Option C is wrong because refusing outright ignores the possibility that the report is genuinely valuable — the change process exists to make that decision properly. Option A is wrong because hidden work is scope creep, and it creates undocumented, untested deliverables.
Exam objective: PMP ECO Task: Manage and control changes (Business Environment)
Q2.A change request has been approved by the change control board. What should the project manager do NEXT?
Explanation: After a change is approved, the project management plan, the affected baselines, and the project documents must be updated to reflect it, and the change must be communicated to all affected stakeholders — before the work is implemented. Without updated baselines, the project has no valid reference for measuring performance. Option B is wrong because implementing without updating the plan leaves the baselines wrong and stakeholders uninformed. Option D is wrong because the change has already been approved; a second approval is unnecessary bureaucracy. Option C is wrong because the decision has been made by the authorized body — the team implements it; they do not vote on it.
Exam objective: PMP ECO Task: Manage and control changes (Business Environment)
Q3.A key supplier has gone bankrupt and can no longer deliver materials the project needs next week. The risk register listed supplier failure as a risk, but no response was planned. What should the project manager do FIRST?
Explanation: The supplier failure has already happened, so it is no longer a risk — it is an issue. The project manager should log it in the issue log, assess its impact on the schedule and cost, and take urgent action to find an alternative supplier. Option C is wrong because updating the risk register does not solve the problem; the event has moved from risk to issue, and it needs issue management. Option A is wrong because acceptance is a strategy for risks that have not yet occurred, not for problems that are already affecting the project. Option D is wrong because waiting wastes the time needed to find an alternative — materials are needed next week.
Exam objective: PMP ECO Task: Remove impediments and manage issues (Business Environment)
Q4.An agile team is blocked because they are waiting for a security approval from another department, and the approval has been delayed for a week. What should the project manager do?
Explanation: A delayed approval that blocks the team is an impediment, and removing impediments is the project manager's job. The project manager should escalate to the security department's management, explain the impact of the delay, and work to get the approval issued. Option B is wrong because asking the team to wait passively wastes a week of capacity and accepts the impediment instead of removing it (though the team can work on other tasks in the meantime, the project manager must still act on the blockage). Option C is wrong because proceeding without a required security approval violates compliance. Option A is wrong because cancelling the sprint is a drastic overreaction to a single impediment — the team can do other work while the project manager clears the blockage.
Exam objective: PMP ECO Task: Remove impediments and manage issues (Business Environment)
Q5.During a sprint, a stakeholder asks a developer directly to add a new feature to the current sprint's work. What should happen?
Explanation: In agile projects, changes are managed through the product backlog: the product owner receives the request, adds it to the backlog, and prioritizes it against existing work for a future sprint. The current sprint's scope is protected so the team can complete what it committed to. Option C is wrong because adding work mid-sprint disrupts the team's commitment and bypasses prioritization. Option A is wrong because developers can speak to stakeholders — the point is that scope decisions go through the product owner, not that communication is forbidden. Option D is wrong because cancelling a sprint is a drastic measure reserved for when the sprint goal becomes obsolete, not for a single feature request.
Exam objective: PMP ECO Task: Manage and control changes (Business Environment)
Q6.A project manager receives a change request that would add $100,000 to the project cost. The change management plan gives the project manager authority to approve changes up to $10,000; larger changes go to the change control board. What should the project manager do?
Explanation: The change exceeds the project manager's approval authority, so it must go to the change control board. The project manager's role is to assess the full impact and present the change (with a recommendation) to the board, which decides. Option C is wrong because approving a change beyond your authority violates the governance framework. Option D is wrong because splitting a change to stay under an approval threshold is a deliberate evasion of the control process. Option A is wrong because rejecting a change without assessment denies the board the opportunity to decide — the change might be worth $100,000, and that is the board's call.
Exam objective: PMP ECO Task: Manage and control changes (Business Environment)
Q7.Two teams working on the same project disagree about who should resolve a technical issue that affects both teams' work. The issue has been open for two weeks. What should the project manager do?
Explanation: An issue that has been open for two weeks because of unclear ownership needs the project manager to act: assign a single owner, agree on a resolution plan with a deadline, and track it in the issue log. Clear ownership is the fix for the disagreement — the issue was stuck because nobody owned it. Option C is wrong because the issue has already been open for two weeks without resolution; leaving it longer will not help. Option B is wrong because escalation is premature — the project manager can resolve the ownership question themselves. Option A is wrong because the project manager resolving a technical issue alone bypasses the teams who own the work and does not build their capability to resolve issues.
Exam objective: PMP ECO Task: Remove impediments and manage issues (Business Environment)
Q8.A change request is submitted to add a feature. The project manager assesses the impact and finds it will add two weeks to the schedule, cost $25,000, and require retraining the support team. What should the project manager include in the assessment presented to the change control board?
Explanation: Integrated change control means assessing a change's impact across the whole project — scope, schedule, cost, quality, risk, resources, and stakeholders — and presenting that full picture to the decision-maker, along with the project manager's recommendation. The board cannot make a sound decision on partial information: the retraining requirement, for example, affects resources and stakeholders, not just cost. Option B and option C are both wrong because they present only one dimension of the impact. Option A is wrong because a recommendation without the supporting impact analysis gives the board no basis for its decision.
Exam objective: PMP ECO Task: Manage and control changes (Business Environment)