PMP Change Control Guide

Change control is one of the most tested PMP topics because it reveals whether a project manager respects governance. The exam does not expect you to reject every change. It expects you to handle change in a way that protects value, scope, schedule, cost, quality, and stakeholder expectations.

The key question is simple: has the project baseline been approved?

When Formal Change Control Applies

In predictive projects, once baselines are approved, changes to scope, schedule, or cost usually require a formal change request. The project manager should not quietly change the plan just because a stakeholder asks.

Formal change control often applies when:

• The scope baseline would change
• The schedule baseline would change
• The cost baseline would change
• A contractual requirement would change
• A regulatory commitment would change
• A key deliverable acceptance criterion would change

The project manager should analyze the impact before submitting or recommending approval. A change control board may approve, reject, or defer the change depending on governance.

What Comes Before the Change Request?

Not every question's first action is "submit a change request." Sometimes the project manager must first understand the request.

If the scenario says a stakeholder asks for a change but the impact is unknown, a good first step is often to evaluate the impact. The change request should include enough information for decision makers.

Look for answers that:

• Review the request
• Analyze impact
• Consult the team or subject matter experts
• Document the change
• Follow the change management plan

Avoid answers that implement the change immediately without approval.

Agile and Backlog Changes

Agile questions use a different control mechanism. If the work is managed through a product backlog, change may be handled by the product owner through prioritization rather than a formal change control board.

In agile scenarios, the best answer may involve:

• Discussing the request with the product owner
• Reprioritizing the backlog
• Reviewing value and impact
• Adding the item to a future iteration
• Protecting the current sprint if appropriate

Do not force predictive change control onto every agile scenario. The exam expects you to match the method to the environment.

Hybrid Change Scenarios

Hybrid projects can be tricky. A software feature may be flexible, while hardware, procurement, or compliance elements may be controlled. If the requested change affects a predictive component, formal change control may still apply.

Read the scenario carefully. The delivery method is not always the same across the whole project.

Common Wrong Answers

Several answer patterns are tempting but usually wrong:

• Tell the team to start work immediately
• Refuse the change because the plan is already approved
• Ask the sponsor to decide before any analysis
• Update the schedule without approval
• Add the feature to the current sprint without product owner involvement

The PMP mindset is balanced. Be responsive to value, but do not bypass governance.

A Practical Decision Rule

If the project is predictive and the baseline changes, use formal change control. If the project is agile and the request affects future work, involve the product owner and backlog. If the impact is unclear, analyze first.

That rule will not answer every question, but it will eliminate many wrong choices quickly.