Page 100 -

4 - PROJECT INTEGRATION MANAGEMENT

The project management plan defines how the project is executed, monitored and controlled, and closed. The
project management plan’s content varies depending upon the application area and complexity of the project. It
is developed through a series of integrated processes extending through project closure. This process results in
a project management plan that is progressively elaborated by updates, and controlled and approved through the
Perform Integrated Change Control (Section 4.5) process. Projects that exist in the context of a program should
develop a project management plan that is consistent with the program management plan. For example, if the
program management plan indicates all changes exceeding a specified cost need to be reviewed by the change
control board (CCB), then this process and cost threshold needs to be defined in the project management plan.

4.2.1 develop Project Management Plan: Inputs

4.2.1.1 Project charter

Described in Section 4.1.3.1. The size of the project charter varies depending on the complexity of the
project and the information known at the time of its creation. At a minimum, the project charter should define
the high-level boundaries of the project. The project manager uses the project charter as the starting point
for initial planning throughout the Initiating Process Group.

4.2.1.2 outputs from other Processes

Outputs from many of the other processes described in Sections 5 through 13 are integrated to create the
project management plan. Any baselines and subsidiary plans that are an output from other planning processes
are inputs to this process. In addition, changes to these documents may necessitate updates to the project
management plan.

4.2.1.3 Enterprise Environmental Factors

Described in Section 2.1.5. The enterprise environmental factors that can influence the Develop Project
Management Plan process include, but are not limited to:
• Governmental or industry standards;

• Project management body of knowledge for vertical market (e.g., construction) and/or focus area
(e.g. environmental, safety, risk, or agile software development);
• Project management information system (e.g., an automated tool, such as a scheduling software tool, a
configuration management system, an information collection and distribution system, or web interfaces
to other online automated systems);

74 ©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Fifth Edition
®

Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
This copy is a PMI Member benefit, not for distribution, sale, or reproduction.