
While Awaiting CCB Decision, Continue Executing Planned Tasks
PMBOK v8 Definition
While awaiting the decision of the change control board (CCB), project managers should continually execute planned tasks while also analyzing the impact and risks related to accepting or rejecting the proposed changes to minimize negative impacts. The CCB is a formally established group responsible for reviewing, evaluating, approving, deferring, or rejecting changes—and for documenting and communicating these decisions. Approved change requests may require new or updated cost estimates, schedule adjustments, resource requirements, and risk assessments.
Why It Matters for the Exam
This concept appears frequently in PMI exam questions about integrated change control and the project manager's role during change processing. Questions test whether you understand that project execution does not stop while waiting for CCB decisions, and that proactive risk analysis of both potential outcomes is required. Expect situational questions where a change request has been submitted, and you must select the correct next action.
Key Points to Remember (for the exam)
- Primary Action: Continue executing planned tasks—do not stop project work while awaiting CCB decisions
- Secondary Action: Analyze impact and risks of both accepting AND rejecting the proposed changes
- Purpose of Analysis: Minimize negative impacts regardless of the CCB's final decision
- CCB Role: Formally established group for reviewing, evaluating, approving, deferring, or rejecting changes
- CCB Output: Documented and communicated decisions about change requests
- Post-Approval Effects: May require new cost estimates, schedule adjustments, resource requirements, and risk assessments
- Plan Updates: Approved changes may require updates to the project management plan and other project documents
Typical PMI Exam Example
A project manager submits a change request to the CCB to replace a critical supplier. While waiting for the CCB decision, what should the project manager do? Answer: Continue executing planned tasks while analyzing the impact and risks of both accepting and rejecting the proposed change.
PMI Exam Traps
-
Trap: Stopping project work until CCB approves the change
- Reality: Project managers should continually execute planned tasks while awaiting decisions
-
Trap: Only analyzing the impact if the change is accepted
- Reality: Analyze impact and risks related to accepting OR rejecting proposed changes
-
Trap: Treating the CCB as optional or informal
- Reality: CCB is a formally established group with documented responsibilities
-
Trap: Assuming CCB approval is the final step
- Reality: Customer or sponsor approval may be required after CCB approval, unless they are CCB members
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Change Control Board (CCB) | Formal authority | CCB reviews, evaluates, approves, defers, or rejects changes |
| Approved Change Requests | Output of CCB | May require new cost estimates, schedule adjustments, resource requirements, risk assessments |
| Project Management Plan | Updated after approval | Approved changes may require updates to the plan and other documents |
| Monitoring and Controlling Focus Area | Process context | Change control is performed during monitoring and controlling activities |
Quick Review Questions
-
While awaiting the CCB's decision on a proposed change, what two actions should the project manager take?
-
What are the five responsibilities of the CCB regarding change requests?
-
After a change request is approved by the CCB, what additional approvals might still be required?
-
What project documents may need updates after a change request is approved?
-
In adaptive approaches, how is project change management typically handled compared to the formal CCB process?
PMBOK v8 Reference
Section 2.1.6.8 - Managing Project Changes (Figure 2-11. Example Flow for Project Changes)