Page 70 -

4 - PROJECT INTEGRATION MANAGEMENT

4.5 Perform Integrated Change Control

See Section 4.5 of the PMBOK Guide, which is applicable for performing integrated change control when
®
managing software projects, with the following extensions.

4.5.1 Perform Integrated Change Control: Inputs

The inputs for performing integrated change control, as presented in the PMBOK Guide, are applicable for
®
performing integrated change control for software projects.

Variations that trigger change control processes differ for different software project life cycles. Control limits
for schedule, cost, defects, and product scope are usually established during initiation and planning for predictive
software project life cycle projects; exceeding a control limit triggers a change control process. For adaptive project
life cycles, formal change control is not usually required for occasional anomalies, as long as the vision and goals
of the project can be achieved within the constraints on project and product scope.

4.5.1.1 Project Management Plan

See Section 4.5.1.1 of the PMBOK Guide.
®

4.5.1.2 Work Performance Reports

®
See Section 4.5.1.2 of the PMBOK Guide.

4.5.1.3 Change Requests

See Section 4.5.1.3 of the PMBOK Guide.
®

4.5.1.4 Enterprise Environmental Factors

See Section 4.5.1.4 of the PMBOK Guide.
®

4.5.1.5 Organizational Process Assets

See Section 4.5.1.5 of the PMBOK Guide.
®

4.5.2 Perform Integrated Change Control: Tools and Techniques

The tools and techniques for performing integrated change control, as presented in Section 4.5.2 of the PMBOK
®
Guide, are applicable for performing integrated change control for software projects.

58 ©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition
®