Change Control Tools
Manual procedures or software that help manage changes and configuration items; at a minimum, they enable the change control board (CCB) to carry out, document, and track its review and approval activities.
Key Points
- May be manual, automated, or a mix, but must support CCB review, approval, and tracking.
- Provide workflows to submit, evaluate, and decide on change requests with an audit trail.
- Integrate with configuration management to maintain baselines and version history.
- Offer reporting and communication features so stakeholders see change status and impacts.
Example
A project team uses a web-based change request system where stakeholders submit changes through a form. The tool routes requests to the CCB agenda, records impact analysis, captures approval or rejection decisions, updates the baseline configuration, and notifies affected team members.
PMP Example Question
Which capability is essential for change control tools used on a project?
- Automatically approve all urgent change requests
- Support the CCB in reviewing, deciding on, and tracking change requests
- Eliminate the need for configuration management
- Guarantee zero scope changes after baseline
Correct Answer: B — Support the CCB in reviewing, deciding on, and tracking change requests
Explanation: Change control tools must at least enable the CCB to perform and document its review, approval, and tracking activities; they do not auto-approve, replace configuration management, or prevent all changes.
