The standard for project management

Autocratic decision making.

 In this decision-making technique, one individual takes the responsibility for 

making the decision for the entire group.

u

u

Multicriteria decision analysis.

 Described in Section 8.1.2.4. This technique uses a decision matrix to provide 

a systematic analytical approach to evaluate the requested changes according to a set of predefined criteria.

---

120 

  

Part 1 - Guide

4.6.2.5 MEETINGS

Change control meetings are held with a change control board (CCB) that is responsible for meeting and reviewing 

the change requests and approving, rejecting, or deferring change requests. Most changes will have some sort of impact 

on time, cost, resources, or risks. Assessing the impact of the changes is an essential part of the meeting. Alternatives 

to the requested changes may also be discussed and proposed. Finally, the decision is communicated to the request 

owner or group.

The CCB may also review configuration management activities. The roles and responsibilities of these boards are 

clearly defined and agreed upon by the appropriate stakeholders and are documented in the change management plan. 

CCB decisions are documented and communicated to the stakeholders for information and follow-up actions.

4.6.3 PERFORM INTEGRATED CHANGE CONTROL: OUTPUTS

4.6.3.1 APPROVED CHANGE REQUESTS

Change requests (described in Section 4.3.3.4) are processed according to the change management plan by the 

project manager, CCB, or an assigned team member. As a result, changes may be approved, deferred, or rejected. 

Approved change requests will be implemented through the Direct and Manage Project Work process. Deferred or 

rejected change requests are communicated to the person or group requesting the change.

The disposition of all change requests are recorded in the change log as a project document update.

4.6.3.2 PROJECT MANAGEMENT PLAN UPDATES

Any formally controlled component of the project management plan may be changed as a result of this process. 

Changes to baselines are only made from the last baseline forward. Past performance is not changed. This protects the 

integrity of the baselines and the historical data of past performance.

4.6.3.3 PROJECT DOCUMENTS UPDATES

Any formally controlled project document may be changed as a result of this process. A project document that is 

normally updated as a result of this process is the change log. The change log is used to document changes that occur 

during a project.

---

��

121