How to Handle an Out-of-Scope Feature Request That Adds Business Value but Increases Risk
During project execution, a key stakeholder requests a feature that is not in the scope. The project manager analyzes the request and determines it would add significant business value but also increase risk. What should the project manager do?
Quick Answer
The correct answer is to initiate a change request and present the trade-offs to the change control board. This is mandated by the PMBOK Guide because any out-of-scope feature, even one with business value, must follow the formal integrated change control process to protect the project baseline. The project manager’s role is not to decide on scope changes unilaterally but to analyze the request, document the trade-off between added business value and increased risk, and let the Change Control Board (CCB) make an informed governance decision. On the PMP exam, this scenario tests your understanding of scope management and change control procedures, often appearing as a trap where you might be tempted to accept the feature due to its business value. The common mistake is to bypass the CCB and negotiate directly with the stakeholder. Memory tip: “Value does not bypass governance—always route scope changes through the CCB.”
⚠ Common exam trap
Watch out — candidates often confuse proactive risk management (Option B) with the mandatory change control process, forgetting that any scope change must first be formally approved by the CCB, not just managed with a contingency plan.
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
✓
Initiate a change request and present the trade-offs to the change control board.
The PMBOK Guide mandates that any out-of-scope feature must go through the formal change control process. By initiating a change request, the project manager documents the trade-offs (business value vs. increased risk) and lets the Change Control Board (CCB) make an informed decision, ensuring alignment with project governance and stakeholder expectations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reject the request to avoid scope creep.
Why it's wrong here
Rejecting discards a request the project manager has already judged to add significant business value, and the project manager lacks authority to dismiss it unilaterally. This tempts as scope-creep protection, but change requests belong in Perform Integrated Change Control for the CCB to assess.
- ✗
Accept the request and manage the risk with a contingency plan.
Why it's wrong here
Accepting bypasses integrated change control, altering scope and baselines without approval, and a contingency plan cannot authorise unapproved scope. This tempts when value seems obvious, but the change request must go through the Perform Integrated Change Control process for evaluation and approval.
- ✓
Initiate a change request and present the trade-offs to the change control board.
Why this is correct
Scope changes must flow through integrated change control, so the project manager documents the request and presents its value, risk and schedule trade-offs to the change control board for a decision, rather than approving or rejecting it unilaterally.
- ✗
Ignore the request because it is out of scope.
Why it's wrong here
Ignoring the request breaches the project manager's duty to record and process every change request through Perform Integrated Change Control, leaving no documented decision. This tempts when the request looks clearly out of scope, yet even rejected requests must be logged, evaluated and formally dispositioned.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PMP question from scratch — 820 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 →
Same concept, more angles
1 more way 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 a project manager overseeing a 12-month ERP implementation. During sprint 6 of 20, the product owner informs you that a key stakeholder wants to add a new reporting module that was not in the original scope. The team estimates this would add 3 weeks to the schedule. What should you do FIRST?
medium- A.Ask the team to begin work on the module immediately to accommodate the stakeholder
- B.Inform the stakeholder that no changes can be made once the project has started
- C.Add the requirement to the product backlog and let the team address it in a future sprint without formal approval
- ✓ D.Submit a change request through the Integrated Change Control process and assess the impact on scope, schedule, and cost
Why D: In a predictive/plan-driven or hybrid environment, any change to baselined scope must go through Integrated Change Control (ICC). The first step is to formally submit a change request and have the team assess impacts on scope, schedule, and cost before a decision is made. This preserves the change control board's authority and ensures the stakeholder's request is evaluated against the project constraints.
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.