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 require 5 additional days. The project is currently on schedule and within budget. Which TWO actions should you take NEXT?
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 evaluate the impact on the project constraints
Options B and D are the correct next steps. Option B is correct because any change to scope outside the current iteration must go through a formal change control process to assess impact on constraints such as time, cost, and quality. Option D is correct because the product owner is responsible for prioritizing the backlog; the new feature should be evaluated against existing items for the next sprint to ensure value delivery. Option A is wrong because adding work to the current sprint without approval violates the change control process and disrupts the sprint commitment. Option C is wrong because using free time for unplanned work undermines transparency and may lead to scope creep without proper assessment. Option E is wrong because completely rejecting a potentially valuable feature without analysis is not agile; the product owner should decide based on priority and value.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add the feature to the current sprint backlog immediately to not delay the release
Why it's wrong here
Adding a new feature directly to the current sprint backlog without formal assessment or approval violates established change control processes, especially in a hybrid environment where baselines are managed. This action risks overcommitting the team, disrupting the current sprint's planned work, and potentially compromising the quality or timely delivery of existing commitments. Such an impulsive decision bypasses necessary impact analysis on project constraints.
- ✓
Submit a change request and evaluate the impact on the project constraints
Why this is correct
Submitting a formal change request is the appropriate PMP response for managing new requirements in a hybrid project, ensuring adherence to the project's governance framework. This process mandates a thorough evaluation of the requested feature's impact on all project constraints, including scope, schedule, cost, resources, and quality. Formal assessment allows stakeholders to make informed decisions about approval, rejection, or deferral, maintaining project control and transparency.
- ✗
Tell the team to implement the feature during any free time
Why it's wrong here
Instructing the team to implement a new feature during 'free time' is unprofessional and undermines project planning and control. This approach bypasses all formal prioritization, resource allocation, and quality assurance processes, potentially leading to unplanned work, technical debt, and a lack of clear accountability. It also disrespects the team's capacity and the structured nature of sprint commitments, whether in a hybrid or purely agile context.
- ✓
Ask the product owner to prioritize the feature against existing backlog items for the next sprint
Why this is correct
Engaging the Product Owner to prioritize the new feature against existing backlog items for a future sprint is a core agile practice within a hybrid framework. The Product Owner is responsible for maximizing product value and strategically ordering the product backlog based on business needs, dependencies, and stakeholder input. This allows for the new feature to be properly assessed, refined, and scheduled without disrupting ongoing work or violating change control for the current iteration.
- ✗
Reject the request because it is outside the original scope
Why it's wrong here
Outright rejecting a request solely because it falls outside the original scope is an inflexible approach that ignores the dynamic nature of projects and stakeholder needs. While the feature may not be in the initial baseline, a robust change control process exists precisely to evaluate and potentially integrate such changes. Dismissing it without assessment misses an opportunity to deliver increased value or adapt to evolving business requirements, which is crucial in a hybrid environment.
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.
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 800 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 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.