How to Control Scope Creep with a Formal Change Control Process
Your project is experiencing scope creep due to informal requests from stakeholders. The project manager wants to establish better control. Which TWO actions should the project manager take?
Quick Answer
Updating the scope management plan addresses scope creep at its structural root: informal requests succeed precisely because there is no clear, agreed-upon process standing in their way, so the fix is to rebuild that process rather than simply refuse individual requests as they arise. A scope management plan spells out how changes are identified, evaluated, and approved, and revisiting it gives the team and stakeholders a shared, documented reference for what counts as a legitimate change request going forward. This is a preventive, process-level fix rather than a reactive one, which is why it pairs naturally with formalizing a change control process more broadly; together they replace ad hoc verbal requests with a traceable workflow that requires evaluation and approval before anything gets incorporated into the project. Simply telling stakeholders no to specific requests, or tightening communication without changing the underlying process, wouldn't stop new informal requests from surfacing the next time a stakeholder has an idea. When an exam scenario describes scope creep driven by informal or undocumented requests, the correct actions are usually the ones that strengthen or reinstate the formal governing plan and process, since that is what closes the gap the informal requests were exploiting in the first place.
⚠ Common exam trap
Many candidates confuse 'managing scope creep' with 'blocking all changes' (Option A) or 'allowing small undocumented changes' (Option C), failing to recognize that the PMBOK mandates a formal, documented process for all changes, regardless of size.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement a formal change control process and educate stakeholders on how to submit change requests
Option D is correct because implementing a formal change control process gives the project manager a structured, documented way to evaluate, approve, or reject change requests, and educating stakeholders on how to submit them channels informal requests into that controlled workflow, directly addressing the scope creep. Option E is correct because the scope management plan defines how scope is defined, validated, and controlled, so reviewing and updating it to clarify the change-handling procedure establishes the governance needed to prevent uncontrolled scope expansion. Option A is not appropriate because categorically declining all requests ignores legitimate changes and bypasses proper evaluation rather than controlling them. Option B is wrong because increasing the budget does not control scope and may even encourage further creep. Option C is wrong because accommodating undocumented low-effort requests perpetuates informal changes and undermines the very control the project manager is trying to establish.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Politely decline all additional requests from stakeholders
Why it's wrong here
Blanket refusal blocks legitimate changes that should flow through the Perform Integrated Change Control process, damaging stakeholder engagement. Declining is tempting as a firm-sounding control, but it is correct only for requests already rejected by the change control board, not as a default response to every stakeholder.
- ✗
Increase the project budget to accommodate potential changes
Why it's wrong here
Adding budget treats the symptom and pre-authorises unapproved scope, leaving the informal request path intact. Contingency reserves are tempting because they exist for approved changes, but they are released only after a change request passes Perform Integrated Change Control, which this scenario lacks.
- ✗
Ask the team to accommodate small requests without documentation if they are low effort
Why it's wrong here
Accepting undocumented low-effort requests institutionalises the informal channel that caused the creep, bypassing the change control board and integrated change control. It appeals as a morale-preserving shortcut, yet it is precisely the correct approach only when a formal change request has been raised, assessed and approved.
- ✓
Implement a formal change control process and educate stakeholders on how to submit change requests
Why this is correct
A formal change control process routes every request through documented assessment, approval and baselining, removing the informal channel that caused scope creep. Educating stakeholders ensures requests are submitted correctly, directly satisfying the stem's need to establish control over unauthorised scope additions.
- ✓
Review and update the scope management plan to clarify how changes will be handled
Why this is correct
The scope management plan defines how scope changes are identified, evaluated and approved. Updating it clarifies the handling of changes, giving the project manager the documented framework needed to prevent informal requests from altering the baseline, which is precisely the control the stem requires.
Go deeper
Related to this question
About these practice questions
This PMP question is part of Courseiva's 820-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on PMP
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are managing a project that is experiencing scope creep. Several stakeholders have been informally requesting additional features directly from team members. Which TWO actions should you take to address this?
medium- A.Refuse all new requests until the project is completed.
- B.Conduct a meeting with stakeholders to review the project scope and re-baseline if necessary.
- C.Update the stakeholder engagement plan to limit stakeholder interactions with the team.
- ✓ D.Educate the team on the importance of following the change control process.
- ✓ E.Remind the team to direct all change requests to the project manager for formal evaluation.
Why D: Option D is correct because the root cause of the scope creep is that team members are accepting informal requests directly, bypassing the change control process; educating the team on why all changes must flow through integrated change control prevents unauthorized work from entering the schedule and budget. Option E is correct because directing all change requests to the project manager ensures each request is formally documented, evaluated for impact on scope, schedule, cost, and risk, and then approved, rejected, or deferred by the change control board rather than being silently absorbed by the team. Together, D and E restore the discipline that stops unapproved features from being added. Option A is wrong because refusing all new requests is not appropriate—legitimate changes should still be evaluated through the change control process rather than blanket-rejected. Option B is wrong because re-baselining the scope is premature and only warranted after approved changes have accumulated; the immediate issue is the informal channel, not the baseline itself. Option C is wrong because limiting stakeholder interactions damages engagement and communication; the goal is to channel requests through the proper process, not to cut stakeholders off.
Variation 2. You are managing a project that is experiencing scope creep. Several stakeholders have been requesting additional features informally. You want to bring the project under control. Which TWO actions should you take?
medium- A.Ignore minor requests to avoid conflict
- ✓ B.Remind stakeholders that all changes must go through the formal change control process
- C.Add the requests to the project backlog without approval
- D.Update the project management plan to reflect all informal requests
- ✓ E.Implement a change request for each informal request to formalize them
Why B: Option B is correct because when scope creep occurs through informal stakeholder requests, the project manager must enforce the Perform Integrated Change Control process, directing all change requests through the Change Control Board (CCB) for review, approval, or rejection before any work is done. Option E is correct because formalizing each informal request as a documented change request (via a Change Request form in the Perform Integrated Change Control process) converts verbal asks into traceable items that can be assessed for impact on scope, schedule, cost, and risk, and then approved or denied. Options A, C, and D are incorrect: ignoring requests (A) allows scope creep to continue unchecked, adding requests to the backlog without approval (C) bypasses the CCB and violates change control, and updating the project management plan to reflect informal requests (D) legitimizes unapproved scope changes without the required analysis and authorization.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMP practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PMP exam.