PMP Process — Managing Technical Aspects Practice Question
You are managing a software development project using a hybrid approach. Midway through the project, the product owner requests a new feature that requires changing the scope and schedule. The team is currently working on a critical path activity. What should you do first?
⚠ Common exam trap
Watch out — candidates often confuse the agile practice of welcoming changes with the need for formal change control in a hybrid project, leading them to incorrectly choose option B or D without considering the critical path and baseline impact.
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 scope, schedule, cost, and quality
In a hybrid project, any change that impacts scope, schedule, cost, or quality must follow the formal change control process. Submitting a change request allows the project manager to evaluate the impact on the critical path, resource allocation, and overall project constraints before any work begins. This aligns with the PMBOK Guide's guidance on integrated change control, ensuring that the change is assessed against the project management plan and baselines.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Tell the product owner the request cannot be considered because the project is already underway
Why it's wrong here
Refusing to consider a new feature request because the project is already underway is an uncollaborative and non-proactive approach. PMI principles emphasize that projects are dynamic, and changes are inevitable throughout the project lifecycle. Dismissing a request outright fails to leverage the integrated change control process, which is specifically designed to evaluate and manage such scenarios, potentially leading to stakeholder dissatisfaction and missed opportunities for value delivery.
- ✗
Add the new feature to the sprint backlog without formal approval
Why it's wrong here
Directly adding a new feature to the sprint backlog without formal approval constitutes a critical deviation from established project governance. Even within a hybrid framework, significant scope alterations necessitate thorough evaluation and approval via the integrated change control process to ensure alignment with project objectives and the project management plan. Bypassing this formal process introduces uncontrolled scope creep, jeopardizes established baselines, and can lead to unmanaged risks and resource overcommitment.
- ✓
Submit a change request and evaluate the impact on scope, schedule, cost, and quality
Why this is correct
Submitting a formal change request is the correct and most responsible procedure for addressing new feature requests in a hybrid project environment. This action initiates the integrated change control process, which systematically evaluates the potential impacts across all project constraints, including scope, schedule, cost, resources, and quality. This rigorous assessment allows for informed decision-making by the change control board (CCB) or relevant stakeholders, ensuring any approved changes are properly integrated and managed, maintaining project integrity and alignment with strategic goals.
- ✗
Ask the team to start working on the feature immediately to save time
Why it's wrong here
Instructing the team to immediately begin work on an unapproved feature is a direct violation of the project management plan and the established change control process. While seemingly efficient, this action bypasses necessary impact analysis and stakeholder approval, leading to uncontrolled scope creep and potential resource misallocation. Such an approach undermines project baselines, introduces unmanaged risks, and can severely compromise the project's ability to meet its original objectives within defined constraints.
Go deeper
Related to this question
Learn chapter
Introduction to the PMP Exam and Project Management Basics
Key term
Team Building
Team building is the process of creating a cohesive group of people who work together effectively toward a shared goal.
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
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.