According to the PMBOK® Guide, the Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating such decisions.
Primary Function: The CCB acts as the " gatekeeper " for the project baselines (Scope, Schedule, and Cost). Their role is to ensure that no change is made to a baseline without a thorough assessment of its necessity and impact.
Authority: The powers and responsibilities of the CCB are defined within the Change Management Plan and the Configuration Management Plan. On many projects, the CCB includes the project sponsor, customer, and functional managers, though the Project Manager often facilitates the meetings.
The Process: When a change request is submitted, it is the CCB ' s duty to review the analysis provided by the project team and make a final decision. This decision is then documented in the Change Log.
Analysis of other options:
A. Responsible for presenting the change: This is typically the responsibility of the Project Manager or the Change Requestor. The CCB receives the presentation; they do not perform the act of presenting to themselves.
B. Analyze the change impact: While the CCB reviews the impact, the actual technical analysis (calculating exactly how many days or dollars a change will cost) is performed by the Project Manager and the Project Team before the CCB meeting occurs.
C. Managing systems: The " management " of the physical software or procedural systems for change and configuration is an administrative task, usually handled by the project management office (PMO) or the project manager, rather than the board members who focus on decision-making.
Per PMI standards, the Change Control Board is essential for maintaining Integrated Change Control, ensuring that all changes are aligned with the project ' s strategic goals and stakeholder expectations.
