Change Control

Change control is the process of reviewing, approving, and managing changes to the project. In predictive projects, baselines are established during planning, and any modifications require formal approval through integrated change control.

Understanding Change in Projects

Change is inevitable in projects, but uncontrolled change leads to scope creep, budget overruns, and schedule delays. Effective change control provides structure for evaluating and implementing necessary changes while protecting project baselines.

Types of Changes

---

Perform Integrated Change Control

Perform Integrated Change Control is the process of reviewing all change requests, approving changes and managing changes to deliverables, project documents, and the project management plan.

Key Characteristics

Process Flow

---

Change Control Board (CCB)

The Change Control Board is a formally constituted group responsible for reviewing, evaluating, and approving/rejecting changes.

CCB Composition

CCB Decision Options

CCB Authority Levels

The Change Management Plan defines CCB composition and authority:

---

Impact Assessment

Before any change is approved, a thorough impact assessment must be conducted:

Areas to Assess

Impact Analysis Steps

1. Document the change request — Clear description of what is requested
2. Identify affected baselines — Which baselines will be modified
3. Assess impact on each baseline — Quantify schedule, cost, scope effects
4. Identify secondary effects — Ripple effects on other areas
5. Evaluate alternatives — Consider different ways to address the need
6. Recommend action — Provide recommendation to CCB

---

Change Log

The Change Log is the document that tracks all change requests throughout the project:

Change Log Contents

---

Configuration Management

Configuration Management ensures that changes to work products are properly identified, documented, and controlled.

Configuration Management Activities

Configuration Management vs. Change Management

Configuration Management Plan

The plan defines:

• Naming conventions for documents and deliverables
• Version control system and procedures
• Document storage and retrieval methods
• Review and approval requirements
• Tools to be used

---

Baseline Updates

When changes are approved, affected baselines must be updated:

Baseline Change Process

Common Baseline Updates

---

Emergency Changes

Some changes cannot wait for formal CCB review:

Emergency Change Criteria

• Immediate action required to prevent harm
• Critical defect affecting operations
• Safety or security concern
• Legal or regulatory requirement

Emergency Change Process

1. Implement — Take immediate action
2. Document — Record what was done and why
3. Report — Notify CCB as soon as possible
4. Formalize — Retrospectively approve the change
5. Update — Modify baselines and documentation

---

Key Takeaways

• Integrated Change Control reviews ALL change requests formally
• The CCB is a formally constituted group that approves or rejects changes
• All changes must be documented in the Change Log
• Impact assessment evaluates effects across all project constraints
• Configuration Management maintains version control of project items
• Approved changes update baselines; rejected changes are documented with rationale
• Emergency changes may be implemented before CCB approval but must be formalized afterward