Change Control Board (CCB)
DE: Aenderungskontrollausschuss (CCB)
A group authorized to review and approve changes to project baselines.
Detailed Explanation
The CCB is a formally constituted group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project. It may include the sponsor, PM, key stakeholders, and subject matter experts.
When a change request is submitted, the CCB assesses impact on scope, schedule, cost, quality, and risk, then makes an informed decision. This prevents unauthorized changes while ensuring beneficial ones proceed efficiently.
In smaller projects, a single person (often the sponsor) may serve as the CCB. In large programs, there may be multiple CCBs at project and program levels handling tactical and strategic changes respectively.
Key Points
- Formally authorized to approve or reject changes
- Reviews impact on scope, schedule, cost, quality, and risk
- Composition varies by project size
- Follows a defined change control process
- Documents all decisions for traceability
- Prevents scope creep while enabling beneficial changes
Practical Example
A developer proposes adding real-time notifications (not in scope). The PM prepares impact analysis: +EUR 15K, +2 weeks, high user value. The CCB approves the schedule extension but asks the team to offset costs elsewhere in the budget.
Tips for Learning and Applying
Define CCB composition and authority in the project management plan
Use a standard change request template for all submissions
Track all decisions and rationale in a change log
Ensure impact analysis is available before CCB meetings
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.