Page 71 -

4 - PROJECT INTEGRATION MANAGEMENT

All proposed changes should be evaluated for impacts on project and product scope, the software team, customers,
users, and other operational stakeholders. Changing the color of an icon on a user display may not be important, or it
may render the application unusable when some users are unable to detect certain colors or when compliance with
disability regulations concerning color blindness may be required. Adding an additional choice on a web page may
have no impact on present capabilities or it may render a data interchange capability inoperable. Therefore, some
changes are minor and others may have significant impacts; all proposed changes need to be evaluated for impact.
4
For predictive software life cycle projects, a change control process typically includes change requests and
change control boards; the change control board may schedule the request at an indicated level of priority, defer
it, or deny it. For adaptive life cycle projects, a change request is another element of the product feature set. An
iteration feature set includes both requests for new features and requests for modifications to existing features; the
content of new and modified features may determine the priority of the features in an iteration feature set.

4.5.2.1 Expert Judgment

See Section 4.5.2.1 of the PMBOK Guide.
®

4.5.2.2 Meetings

See Section 4.5.2.2 of the PMBOK Guide.
®

4.5.2.3 Change Control Tools

See Section 4.5.2.3 of the PMBOK Guide.
®

4.5.3 Perform Integrated Software Change Control: Outputs

®
See Section 4.5.3 of the PMBOK Guide for outputs applicable to performing integrated change control for
software projects.

4.5.3.1 Approved Change Requests

See Section 4.5.3.1 of the PMBOK Guide.
®

4.5.3.2 Change Log

®
See Section 4.5.3.2 of the PMBOK Guide.

4.5.3.3 Project Management Plan Updates

See Section 4.5.3.3 of the PMBOK Guide.
®

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