PMP Process — Managing Technical Aspects Practice Question
You are managing a software development project using a hybrid approach. During a sprint review, the product owner requests a new feature that was not in the backlog. The team estimates it will take 5 days to implement. What is the BEST action to take?
⚠ Common exam trap
PMP often tests whether candidates bypass change control for 'small' changes — the trap is choosing the expedient agile-sounding answer instead of the disciplined change-request 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 and assess the impact on the project baseline.
In a hybrid project with a defined baseline, a new feature request from the product owner during a sprint review is a scope change that must go through the integrated change control process. Submitting a change request and assessing impact on the baseline ensures the change is evaluated for scope, schedule, cost, and risk before approval. This preserves governance even in agile-hybrid environments.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Submit a change request and assess the impact on the project baseline.
Why this is correct
In a hybrid project environment, any new feature, regardless of its perceived size or origin, necessitates a formal evaluation. Submitting a change request initiates the integrated change control process, allowing for a thorough assessment of its potential impact on the project's scope, schedule, cost, quality, and resource baselines. This structured approach ensures that any approved modifications are properly documented and integrated, maintaining project control and preventing unauthorized scope creep in alignment with PMP principles.
- ✗
Tell the product owner that no changes are allowed until the project is completed.
Why it's wrong here
This approach is overly rigid and counterproductive, especially in a hybrid or agile context where adaptability and continuous stakeholder collaboration are highly valued. Preventing all changes until project completion ignores the dynamic nature of project requirements and stakeholder needs, potentially leading to a final product that no longer meets current business objectives or market demands. PMP principles advocate for managing changes through a structured process, not outright rejection, to ensure project success and sustained stakeholder satisfaction.
- ✗
Ask the team to include it in the next sprint and inform the product owner.
Why it's wrong here
While involving the team and informing the product owner are valuable communication practices, simply adding a new feature to the next sprint without formal evaluation and approval bypasses the integrated change control process. This action risks introducing unapproved scope, potentially impacting the project's baselines for schedule, cost, and resources without proper assessment or formal authorization. It undermines the project manager's responsibility to manage scope and maintain control over the project's direction and objectives.
- ✗
Add the feature to the current sprint as it's small and the team can handle it.
Why it's wrong here
Adding a new feature directly to the current sprint, even if perceived as small or easily manageable by the team, constitutes unauthorized scope addition, commonly referred to as gold-plating. This action directly violates the project's established change control process and can lead to unmanaged scope creep, potentially consuming valuable resources, time, and budget without formal approval or impact assessment. It undermines project governance and the integrity of the project baselines, regardless of the team's immediate capacity.
Go deeper
Related to this question
Learn chapter
Planning Project Scope and Requirements
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.
Key term
Scrum Methodology
Scrum is a lightweight process framework that helps teams deliver complex projects in small, iterative chunks called sprints.
About these practice questions
One of 820 original PMP practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
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.