Page 59 -

4 - PROJECT INTEGRATION MANAGEMENT

4.1.1 Develop Project Charter: Inputs

The inputs in Section 4.1.1 of the PMBOK Guide are applicable for developing a software project charter.
®

4.1.1.1 Project Statement of Work

See Section 4.1.1.1 of the PMBOK Guide. 4
®

4.1.1.2 Business Case

See Section 4.1.1.2 of the PMBOK Guide.
®
In addition, the business case for a software product, and particularly for an enterprise system, should address
total cost of ownership, to include anticipated operational and sustainment costs.

4.1.1.3 Agreements

See Section 4.1.1.3 of the PMBOK Guide.
®

4.1.1.4 Enterprise Environmental Factors

See Section 4.1.1.4 of the PMBOK Guide.
®

4.1.1.5 Organizational Process Assets

See Section 4.1.1.5 of the PMBOK Guide.
®

4.1.2 Develop Project Charter: Tools and Techniques

The tools and techniques presented in Section 4.1.2 of the PMBOK Guide are applicable for developing a
®
software project charter with the following additional considerations.

Domain experts should be consulted when developing a software project charter. Expertise in developing similar
systems using similar development platforms, systems software, product architecture, and information design (i.e.,
databases, data interchanges, and data warehouses) may provide valuable insights and expose unrecognized complexities
and risk factors. In addition, when software projects involve working with existing software, inputs from experts familiar
with the architecture, technical implementation, and/or testing approach can provide assistance in developing the project
charter. Those familiar with the project team (when known) can provide inputs concerning team capabilities.

4.1.2.1 Expert Judgment

See Section 4.1.2.1 of the PMBOK Guide.
®

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