PMP Process — Managing Technical Aspects Practice Question
You are the project manager for a software development project using a hybrid approach. During the sprint review, the product owner is satisfied with the deliverables, but one key stakeholder requests a significant change that would add a new feature. The team has already started planning the next sprint. What should you do FIRST?
⚠ Common exam trap
Many exam-takers confuse the agile principle of welcoming changes with the need for formal governance in a hybrid approach, leading them to choose Option B without considering the change control process.
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
✓
Submit a change request to the change control board for evaluation and approval.
In a hybrid project, changes are managed through a formal change control process. The stakeholder's request for a new feature is a significant change that must be evaluated for impact on scope, schedule, and budget before any action is taken. Submitting a change request to the change control board (CCB) ensures proper governance and prevents unauthorized scope creep, which is critical when the team has already begun planning the next sprint.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Refuse the change because the scope was already agreed upon during sprint planning.
Why it's wrong here
Refusing a proposed change simply because the scope was previously agreed upon during sprint planning is contrary to effective project management principles. PMI emphasizes that all change requests, regardless of when they arise, must undergo a formal evaluation process to assess their potential impact and value. This approach is rigid and fails to acknowledge the dynamic nature of projects, where legitimate changes may be necessary to meet evolving business needs or stakeholder requirements.
- ✗
Ask the team to include the new feature in the next sprint since it's a high priority for the stakeholder.
Why it's wrong here
Directly asking the team to incorporate a new feature into the next sprint based solely on a stakeholder's high priority, without formal evaluation and approval, constitutes unauthorized scope creep. This action bypasses the critical Integrated Change Control process, which is essential for assessing the impact on project baselines, resources, and overall project objectives. Implementing changes without proper review and approval can lead to budget overruns, schedule delays, and compromised quality.
- ✗
Advise the stakeholder to wait until the project is complete and then submit an enhancement request.
Why it's wrong here
Advising a stakeholder to delay a potentially valuable change until the project is complete and then submit an enhancement request is not a proactive or efficient project management practice. The Integrated Change Control process is specifically designed to evaluate and manage changes throughout the project lifecycle, allowing for timely incorporation if deemed beneficial and approved. Postponing evaluation can lead to missed opportunities, stakeholder dissatisfaction, or significantly higher costs for implementation later.
- ✓
Submit a change request to the change control board for evaluation and approval.
Why this is correct
Submitting a change request to the Change Control Board (CCB) for evaluation and approval is the correct and most appropriate action according to PMI's Integrated Change Control process. This ensures that any proposed change, whether minor or significant, is formally documented and thoroughly assessed for its impact on project baselines, resources, and strategic objectives. The CCB's role is to make an informed decision to approve, reject, or defer the change, maintaining control over the project's evolution.
Go deeper
Related to this question
Learn chapter
Introduction to the PMP Exam and Project Management Basics
Key term
Scrum Methodology
Scrum is a lightweight process framework that helps teams deliver complex projects in small, iterative chunks called sprints.
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.