PMP Process — Managing Technical Aspects Practice Question
Your project is a software implementation using a hybrid approach. The team has been facing scope creep due to informal change requests from stakeholders. Which TWO actions should you take to address this issue?
⚠ Common exam trap
Candidates often confuse accommodating scope creep (e.g., adding buffers) with preventing it, or they overreact by rejecting all changes, failing to recognize that a formal process is the balanced, PMBOK-aligned solution that manages changes without derailing the project.
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 require all changes to go through it
Implementing a formal change control process ensures that all scope changes are evaluated, approved, and documented before being integrated into the project. This directly addresses the root cause of scope creep—informal requests—by enforcing a structured workflow that includes impact analysis, approval gates, and baseline updates. In a hybrid software implementation, this process aligns with both predictive and agile practices, preventing unauthorized changes from disrupting the development cycle.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reject all scope changes for the remainder of the project
Why it's wrong here
Arbitrarily rejecting all future scope changes is an inflexible and unsustainable approach in project management, particularly in a hybrid environment where some adaptability is expected. This strategy can lead to missed opportunities for valuable improvements, stakeholder dissatisfaction, and a final product that fails to meet evolving business needs or market demands. Effective scope management requires evaluation, not outright refusal, of all proposed changes.
- ✗
Add a contingency buffer to the schedule to absorb future changes
Why it's wrong here
Adding a contingency buffer to the schedule is a risk management technique intended to address identified risks or known unknowns, not to accommodate uncontrolled scope creep. This action would implicitly sanction informal scope expansion, failing to address the root cause of the issue, which is a lack of formal change control. True scope management requires proactive control, not merely creating slack to absorb unapproved work.
- ✗
Stop all work until the scope is re-baselined
Why it's wrong here
Stopping all project work until the scope is re-baselined is an extreme and often unnecessary measure that can severely impact project timelines and budget. While re-baselining might be required for significant, approved changes, halting all progress due to ongoing scope creep is inefficient, causes significant delays, and wastes resources. Effective scope control focuses on managing changes through established processes rather than resorting to a complete project standstill.
- ✓
Implement a formal change control process and require all changes to go through it
Why this is correct
Implementing a formal change control process is the foundational project management practice for effectively managing scope and preventing uncontrolled creep. This process ensures that all proposed changes are formally documented, reviewed for impact on scope, schedule, and cost, and approved or rejected by authorized stakeholders before implementation. It maintains the integrity of the project baseline and provides a structured mechanism for managing evolving requirements.
- ✓
Educate stakeholders on the impact of scope changes and the need to follow the change control process
Why this is correct
Educating stakeholders on the potential impacts of scope changes and the necessity of adhering to the formal change control process is crucial for proactive scope management. This communication fosters a shared understanding of how changes affect project baselines, resources, and timelines, thereby reducing informal requests and promoting compliance. Engaged and informed stakeholders are more likely to follow established procedures, significantly mitigating scope creep.
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.