PMP Process — Managing Technical Aspects Practice Question
You are managing a software development project using a hybrid approach. During a sprint review, the customer expresses satisfaction but requests a small additional feature that was not in the original backlog. The team believes it can be completed in two days without affecting the critical path. What should you do first?
⚠ Common exam trap
PMP often tests the misconception that small changes can bypass the change control process, but the exam expects you to always follow formal change control for any scope change.
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, any change to the baseline scope—even a small one—must go through the formal change control process. The change control board (CCB) evaluates the impact on scope, schedule, cost, and quality before approval. Submitting a change request ensures the change is properly assessed and documented, maintaining the integrity of the project management plan.
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 to the change control board for evaluation and approval.
Why this is correct
This is the correct action as it adheres to the Integrated Change Control process, a fundamental principle in project management. All proposed changes, regardless of their perceived size or origin, must be formally documented as a change request and submitted to the Change Control Board (CCB). The CCB is responsible for evaluating the potential impact on project baselines (scope, schedule, cost, quality, resources, risks) and making an informed decision for approval or rejection, ensuring proper governance and preventing uncontrolled scope creep.
- ✗
Ask the team to implement the feature and document it as a scope change later.
Why it's wrong here
Asking the team to implement a feature and document it later is a critical violation of project governance and the Integrated Change Control process. This approach bypasses the necessary formal impact analysis and approval, leading to unauthorized work and a high risk of uncontrolled scope creep. Proceeding without formal approval undermines the project management plan and can result in unbudgeted costs, schedule delays, and a lack of stakeholder alignment.
- ✗
Inform the customer that no changes are allowed after the sprint review.
Why it's wrong here
Informing the customer that no changes are allowed after a sprint review is an inappropriate response and demonstrates poor stakeholder management. While changes must be managed, outright refusal without evaluation contradicts the principle of customer collaboration and flexibility, even in a hybrid environment. The project manager's role is to facilitate the formal change process, not to unilaterally deny requests without proper assessment through the established change control mechanism.
- ✗
Approve the request since it is small and won't affect the schedule.
Why it's wrong here
Approving a change request unilaterally, even if it appears small, is a direct violation of the project management plan and the Integrated Change Control process. Such an action bypasses the necessary formal impact analysis by the Change Control Board, which is crucial for assessing the cumulative effect of 'small' changes on project baselines. This practice inevitably leads to scope creep, potential budget overruns, and schedule delays, as the true impact is not formally evaluated or documented.
Go deeper
Related to this question
Learn chapter
Managing Team Conflict and Performance
Key term
Project Management Plan
A formal, approved document that defines how a project is executed, monitored, controlled, and closed, serving as the single source of truth for the project team.
Key term
Training and Development
Training and Development is the process of enhancing team members' skills, knowledge, and competencies to improve project performance and achieve career growth.
About these practice questions
This PMP question is part of Courseiva's 820-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
8 more ways this is tested on PMP
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. 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?
medium- A.Add the feature to the current sprint backlog immediately to not delay the release
- ✓ B.Submit a change request and evaluate the impact on the project constraints
- C.Tell the team to implement the feature during any free time
- ✓ D.Ask the product owner to prioritize the feature against existing backlog items for the next sprint
- E.Reject the request because it is outside the original scope
Why B: Option B is correct because in a hybrid project any new feature requested mid-sprint is a scope change that must go through the change control process, where its impact on the triple constraints (scope, schedule, cost) and other baselines is formally evaluated before approval. Option D is correct because the product owner owns backlog prioritization, so the new feature should be compared against existing backlog items and, if approved, scheduled into a future sprint rather than disrupting the current one. Option A is wrong because injecting unplanned work into the active sprint undermines the sprint goal and the team's committed capacity, and it bypasses change control. Option C is wrong because directing the team to work on unapproved scope during 'free time' is uncontrolled scope creep and ignores the change management process. Option E is wrong because rejecting the request outright is premature; the request should be evaluated and prioritized, not dismissed, since the project is on schedule and within budget.
Variation 2. You are managing a project using a hybrid approach. During a sprint, the development team discovers a critical security vulnerability that was not identified during risk planning. The fix will require significant rework and will cause the sprint goal to be missed. What should the project manager do FIRST?
hard- ✓ A.Perform an impact analysis and submit a change request to address the vulnerability
- B.Instruct the team to fix the vulnerability immediately without formal change control
- C.Ask the team to work overtime to fix the vulnerability while still achieving the sprint goal
- D.Allow the team to continue with the sprint and address the vulnerability in a future sprint
Why A: The project manager should first assess the impact of the security vulnerability on scope, schedule, and cost, then submit a change request to formally address the issue. Option B is incorrect because bypassing change control violates project governance, especially in a hybrid approach where change management processes are defined. Option C is incorrect because requiring overtime to achieve the sprint goal ignores the rework impact and could lead to burnout and quality issues. Option D is incorrect because delaying the fix leaves the vulnerability unaddressed, which is unacceptable for a critical security issue.
Variation 3. You are the project manager for a software development project using a hybrid approach. During a sprint review, the product owner requests a significant change to a feature that has already been accepted in a previous sprint. The change would require rework and impact the critical path. What should you do FIRST?
medium- A.Add the change to the product backlog for a future sprint without formal approval
- ✓ B.Submit a change request and evaluate the impact on the project constraints
- C.Instruct the team to implement the change immediately to maintain stakeholder satisfaction
- D.Reject the change because the feature was already accepted
Why B: In a hybrid project, changes to accepted deliverables must follow a formal change control process. Submitting a change request (Option B) ensures the impact on the critical path, schedule, and budget is evaluated before any rework begins, aligning with the PMBOK Guide's guidance on integrated change control.
Variation 4. 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?
medium- A.Refuse the change because the scope was already agreed upon during sprint planning.
- B.Ask the team to include the new feature in the next sprint since it's a high priority for the stakeholder.
- C.Advise the stakeholder to wait until the project is complete and then submit an enhancement request.
- ✓ D.Submit a change request to the change control board for evaluation and approval.
Why D: 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.
Variation 5. You are the project manager for 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 believes it can be completed within the current sprint without impacting the sprint goal. What should you do FIRST?
medium- ✓ A.Submit a change request to the change control board to evaluate the impact on the project.
- B.Add the feature to the product backlog for prioritization in a future sprint.
- C.Ask the team to implement the feature immediately since it won't affect the sprint goal.
- D.Allow the product owner to approve the change since it is within the sprint.
Why A: In a hybrid project with a formal change control process, any new scope request—even one raised during a sprint review—must first go through the change control board (CCB) so its impact on scope, schedule, cost, and risk can be evaluated before any work is committed; option A is therefore the correct first step. Although the team believes the feature fits within the current sprint, that informal assessment does not replace the governance step of submitting a change request. Option B defers the request without evaluation, option C bypasses change control by starting work immediately, and option D wrongly assumes the product owner can unilaterally approve scope changes within the sprint.
Variation 6. You are the project manager for a software development project using a hybrid approach. During a sprint review, the product owner requests a change that would add a new feature to the current release. The team estimates it will take two additional sprints. What should you do first?
medium- A.Ask the team to start working on the new feature immediately to meet the stakeholder's needs
- ✓ B.Submit a change request through the Integrated Change Control process to assess the impact on scope, schedule, cost, and quality
- C.Explain that no changes can be made after the sprint review to maintain the schedule
- D.Add the feature to the backlog and prioritize it for the next release without further analysis
Why B: In a hybrid project management approach, changes that affect scope, schedule, cost, or quality must go through Integrated Change Control (ICC) per PMBOK. Even in an agile/hybrid context, a change adding two sprints of work is a significant scope change that requires formal impact analysis and approval before commitment. Submitting a change request first ensures the product owner, sponsor, and team understand the trade-offs before any work begins.
Variation 7. You are managing a software development project using a hybrid approach. In the middle of a sprint, you discover that a team member has been working on a feature that was de-scoped in the last sprint review. The team member claims the product owner informally agreed to add it back. What should you do FIRST?
medium- A.Ask the product owner to formally document the agreement and add it to the backlog
- ✓ B.Stop work on the feature and initiate a change request through the change control process
- C.Allow the team member to continue since the product owner agreed
- D.Escalate to the project sponsor for a decision
Why B: In a hybrid project, scope changes must follow a formal change control process to maintain baseline integrity. The team member's informal agreement with the product owner bypasses this, risking scope creep and unapproved work. Stopping work and initiating a change request ensures proper evaluation of impact on schedule, budget, and sprint goals before proceeding.
Variation 8. 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?
medium- A.Tell the product owner the request cannot be considered because the project is already underway
- B.Add the new feature to the sprint backlog without formal approval
- ✓ C.Submit a change request and evaluate the impact on scope, schedule, cost, and quality
- D.Ask the team to start working on the feature immediately to save time
Why C: 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.
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.