PMP Process — Managing Technical Aspects Practice Question
Your project is experiencing scope creep due to informal change requests from stakeholders. Which TWO actions should you take to address this?
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
✓
Review the change management plan with stakeholders and remind them of the formal change control process
Options A and B are correct. Option A reinforces the change control process by reminding stakeholders of the formal procedure. Option B ensures that informal requests are documented and assessed for potential change requests. Option C is incorrect because the project manager should not instruct the team to bypass the formal process. Option D is incorrect because ignoring requests is not proactive. Option E is incorrect because the sponsor should not be the first point of contact for managing scope creep.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Review the change management plan with stakeholders and remind them of the formal change control process
Why this is correct
This is a primary corrective action because it directly addresses the root cause of scope creep: a deviation from the established change control process. By reviewing the change management plan with stakeholders, the project manager reinforces the agreed-upon procedures for submitting, evaluating, and approving changes. This proactive communication educates stakeholders on the formal process, clarifies expectations, and helps re-establish adherence to the project's governance framework, thereby mitigating further informal scope additions.
- ✓
Document all requests in the issue log and assess them for potential change requests
Why this is correct
Documenting all requests, even informal ones, in the issue log is a crucial step in managing scope creep and maintaining project control. This action ensures transparency by creating a formal record of all proposed changes, allowing for proper assessment against project objectives and constraints. It facilitates the evaluation process by providing a structured way to determine which requests warrant a formal change request and subsequent review by the Change Control Board, preventing unmanaged work from entering the project scope.
- ✗
Tell the project team to reject any work not approved by you
Why it's wrong here
Instructing the project team to reject work not personally approved by the project manager is an inappropriate response that centralizes control excessively and bypasses established project governance. This approach undermines the formal change control process, which typically involves a Change Control Board (CCB) or a defined approval hierarchy, not just the PM. It also fails to address the underlying stakeholder behavior causing informal requests and can lead to team confusion, resentment, and a breakdown in communication with stakeholders.
- ✗
Ignore informal requests until a formal change request is submitted
Why it's wrong here
Ignoring informal requests until a formal change request is submitted is a detrimental approach to stakeholder management and project communication. While formal processes are essential, completely disregarding informal input can damage stakeholder relationships, erode trust, and make stakeholders feel unheard or disrespected. This can lead to increased frustration, potential project delays as stakeholders find alternative ways to implement their needs, or even active resistance, ultimately hindering project success and collaboration.
- ✗
Ask the project sponsor to intervene and stop stakeholders from making requests
Why it's wrong here
Asking the project sponsor to intervene and stop stakeholders from making requests is an abdication of the project manager's direct responsibility for managing project processes and stakeholder expectations. The project manager is accountable for enforcing the change management plan and engaging stakeholders to ensure adherence to formal procedures. Prematurely escalating a process adherence issue to the sponsor undermines the PM's authority and capability to manage the project independently, potentially signaling a lack of control.
Go deeper
Related to this question
Learn chapter
Introduction to the PMP Exam and Project Management Basics
Key term
Change Control Process
A formal, structured procedure used to manage any changes to a project's scope, schedule, budget, or requirements, ensuring every modification is reviewed, approved, tested, and documented before implementation.
About these practice questions
Courseiva writes every PMP question from scratch — 800 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
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.