Page 63 -

4 - PROJECT INTEGRATION MANAGEMENT

frequently during software development. Without effective version control, the incorrect version of a software
module may be used as the basis for further work or may be incorrectly integrated into a demonstrable or
deliverable product baseline.

Some software projects use formal governance mechanisms to maintain control of software artifacts, such as
a software change control board. Other software projects use frequent demonstrations of working software and
consultations with the customer or user representative to agree on changes to be made. 4

4.2.2 Develop Project Management Plan: Tools and Techniques

The tools and techniques in Section 4.2.2 of the PMBOK Guide are applicable for developing a software project
®
management plan. Templates and estimation tools are useful when developing a software project plan.

4.2.2.1 Expert Judgment

®
See Section 4.2.2.1 of the PMBOK Guide.

4.2.2.2 Facilitation Techniques

®
See Section 4.2.2.2 of the PMBOK Guide.

4.2.3 Develop Project Management Plan: Outputs

4.2.3.1 Project Management Plan

See Section 4.2.3.1 of the PMBOK Guide. In addition, the following plans may be included as supporting outputs:
®
• Requirements management plan,
• Configuration management plan,

• Security plans (physical, project, data),
• Quality management plan,
• Enterprise technology insertion plan,

• Information security plan,
• Test and evaluation plan,

• Information management plan,
• Release and deployment plan,

• Technology infrastructure plan, and
• Project-specific training plan for the software team.

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