When CCB Denies Changes but Stakeholder Demands New Requirements, What Should You Do?
You are a project manager in a projectized organization. The project is nearing completion, but a key stakeholder has introduced several new requirements that were not in the original scope. The stakeholder insists these are critical for user acceptance. The project is already behind schedule and over budget. The change control board (CCB) has denied all previous change requests due to time and cost constraints. What is the best course of action?
Quick Answer
The answer is to submit a change request for the new requirements and let the CCB decide. This is correct because the change control board is the formal authority for approving or denying scope changes, regardless of stakeholder pressure or project constraints; bypassing the CCB violates the established change control process and undermines project governance. On the CAPM exam, this scenario tests your understanding of the integrated change control process and the project manager’s role as a facilitator, not a decision-maker—a common trap is assuming you can accommodate stakeholders directly to avoid conflict, but the exam emphasizes following formal procedures even when the CCB has a history of denial. Remember the memory tip: “When in doubt, route it out”—always route new requirements through the CCB to maintain control and documentation.
⚠ Common exam trap
The trap is thinking that stakeholder urgency overrides the change control process, leading candidates to choose options that bypass the CCB.
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 for the new requirements and let the CCB decide
In a projectized organization with a formal change control process, any change to scope must go through the CCB. Even though the stakeholder insists the requirements are critical, the project manager cannot unilaterally accept them. The correct action is to submit a change request to the CCB for evaluation, as they are the designated authority to approve or deny changes based on project constraints.
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 requirements to the project but delay completion to accommodate them
Why it's wrong here
Unilaterally adding requirements and extending the schedule bypasses the CCB, whose denial is binding, and ignores the approved baseline. It is tempting because stakeholder acceptance feels urgent, and this action would be correct only if the change were approved through integrated change control.
- ✗
Accept the new requirements to satisfy the stakeholder and update the project plan
Why it's wrong here
Accepting the requirements and updating the plan circumvents the CCB's denial and alters the approved scope, schedule, and cost baseline without authorisation. It is tempting because satisfying a key stakeholder appears to secure acceptance, and this would be correct only after the change passed through integrated change control.
- ✗
Explain to the stakeholder that changes are not possible and close the project as planned
Why it's wrong here
Closing the project ignores the stakeholder's user-acceptance requirements and the CCB's authority to reassess scope; the project manager should escalate the new requirements to the CCB for evaluation rather than unilaterally refusing them. This option tempts because closing as planned suits a project with no outstanding change requests, but here acceptance criteria are unresolved.
- ✓
Submit a change request for the new requirements and let the CCB decide
Why this is correct
Scope changes must flow through integrated change control regardless of prior denials. Submitting a change request documents the new requirements, lets the CCB assess impact against time and cost constraints, and preserves the project manager's authority limits in a projectised organisation.
Go deeper
Related to this question
About these practice questions
This CAPM question is part of Courseiva's 451-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
1 more way this is tested on CAPM
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. A project manager is managing a complex IT project with many inter-dependencies. During execution, a key stakeholder requests a feature that will require rework of several completed deliverables. The project manager wants to minimize disruption to the project. What is the best course of action?
hard- A.Delegate the decision to the change control board (CCB)
- ✓ B.Follow the integrated change control process to assess impact
- C.Implement the change immediately to satisfy the stakeholder
- D.Refuse the request as it will cause rework
Why B: Following the integrated change control process ensures that the change request is formally assessed for its impact on scope, schedule, cost, and quality before a decision is made. This minimizes disruption by evaluating the change systematically and involving the change control board (CCB) as needed.
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 CAPM 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 CAPM exam.