PMP: Integration Management

Project Integration Management is the conductor of the project management orchestra. It’s the discipline that unifies, coordinates, and directs all other knowledge areas and project activities into a cohesive whole. For the Project Management Professional (PMP)® candidate, mastering integration is non-negotiable; it’s the core process that ensures your project charter, plan, execution, and closure are logically connected and aligned with stakeholder expectations. Without effective integration, a project is merely a collection of disconnected tasks destined for confusion and failure.

The Central Philosophy: Unifying the Project

Before diving into the specific processes, you must understand the fundamental philosophy. Project Integration Management is the overarching framework that coordinates the processes and activities within all other knowledge areas—Scope, Schedule, Cost, Quality, Resources, Communications, Risk, Procurement, and Stakeholder Management. Think of it as the central nervous system of your project. It makes trade-off decisions, resolves conflicts between competing objectives, and ensures that the project management plan remains a viable, integrated document. Your primary tool as a project manager is not just creating plans but synthesizing information from all domains to guide the project to successful completion.

Initiation and Planning: Charter and Plan

The project officially begins here. The project charter is a document issued by the project sponsor that formally authorizes the project’s existence and provides you, the project manager, with the authority to apply organizational resources. It is a foundational input to all planning processes. For the PMP exam, you must know that the charter includes high-level information: the project’s purpose, measurable objectives, key success criteria, high-level risks, a summary milestone schedule, a pre-approved budget, a list of key stakeholders, and the assigned project manager with their authority level. Crucially, the charter formally links the project to the organization’s ongoing work and strategic goals. You cannot proceed with detailed planning without this signed document, as it establishes the project’s business case and your right to lead it.

This is where integration becomes tangible. The project management plan is not a single document but a collection of subsidiary plans and baselines from all knowledge areas, integrated into a coherent whole. Your job is to facilitate its development by guiding the planning efforts of your team and specialists. The plan includes the scope, schedule, and cost baselines, along with management plans for requirements, quality, resources, communications, risk, procurement, and stakeholder engagement. A critical component is the change management plan, which is part of the overall project management plan and defines how changes will be formally processed. The integrated project management plan is your primary guide for how the project will be executed, monitored, controlled, and closed. It must be approved by key stakeholders before execution begins.

Execution and Monitoring: Doing and Tracking the Work

This is the process of leading, performing, and carrying out the work defined in the project management plan. Directing and managing project work involves executing the planned activities to produce the project deliverables, managing technical and organizational interfaces, implementing approved changes, and creating work performance data. It’s an active, day-to-day process where you are constantly applying your integration skills. You are not just ensuring tasks are done; you are ensuring they are done in alignment with the integrated plan, making real-time decisions that balance scope, time, cost, quality, and risk. The outputs of this process include deliverables, work performance data, and updates to project documents. Any deviation from the plan that requires a formal adjustment is funneled into the change control process.

While work is being executed, you must constantly track, review, and report on overall project performance. Monitoring and controlling project work is the process of comparing actual performance against the project management plan. This involves analyzing work performance data (raw observations) to create work performance information (contextualized data), which is then used to generate work performance reports (formatted summaries for stakeholders). You are integrating data from across all knowledge areas—Is the team burning through the budget faster than planned? Are deliverables meeting quality standards? Are new risks emerging?—to assess the project’s health. The key output is change requests, which are recommendations to bring project performance back in line with the plan or to adjust the plan itself based on new information. These requests are then processed through the next critical process.

Control and Closure: Managing Changes and Ending the Project

This is arguably the most critical process for maintaining project integrity. Perform Integrated Change Control (ICC) is the formal review process for all change requests. No change to any project baseline (scope, schedule, cost) or component of the project management plan is implemented without going through this process. The ICC process is performed by a Change Control Board (CCB), which you often chair. You are responsible for ensuring every change request is evaluated for its impact on all aspects of the project—an integrated assessment. What seems like a simple scope change can have cascading effects on the schedule, cost, quality, risk, and resources. Approved changes are implemented via updates to the project management plan and project documents, and their implementation is then tracked. This rigorous process protects the project baselines and ensures only value-adding changes are incorporated.

Formal closure is an integration activity. The closing process group includes finalizing all activities across all project phases or for the entire project. You must ensure all work is completed, obtain formal acceptance of deliverables from the sponsor or customer, and finalize any open claims or procurement contracts. A key output is the final report, which provides a summary of project performance and the business value delivered. Furthermore, you conduct lessons learned sessions to capture knowledge for future projects and archive all project documents. Closing is not an afterthought; it’s a planned, integrated process that provides organizational value, administrative closure, and releases the project team. For the PMP, know that a project can be terminated early, and you must still perform a closure process to document the reasons and current status.

Common Pitfalls

1. Treating the Project Charter as Optional: A major red flag is beginning detailed planning without a signed charter. On the exam, if a scenario describes a project manager starting to create a WBS or schedule without a charter, it’s a violation of proper process. The charter provides the necessary authority and business justification.
2. Bypassing Integrated Change Control: The most common project failure mode is implementing changes informally. If a team member, or even a stakeholder, asks for a “small change” and you agree without submitting a change request and assessing its integrated impact, you are undermining the project baselines. The PMP exam will test your discipline to always follow the formal ICC process.
3. Confusing Work Performance Data, Information, and Reports: These are distinct concepts. Data is raw measurements (e.g., activity completed, cost spent). Information is analyzed data in context (e.g., CPI = 0.9, indicating a cost overrun). Reports are formal presentations of information (e.g., a monthly status report for the steering committee). Mixing them up can lead to incorrect answers.
4. Neglecting Formal Project Closure: Many project managers rush to the next assignment. For the PMP, a project is not complete until formal administrative and contractual closure is performed, lessons learned are documented, and archives are created. Failing to do this leaves organizational knowledge on the table and can cause legal or financial issues.

Summary

• Project Integration Management is the central coordinating function for all project activities and knowledge areas, ensuring the project is managed as a unified endeavor.
• The Project Charter formally authorizes the project and the project manager, providing the foundation for all subsequent planning.
• The Project Management Plan is the integrated, approved compilation of all subsidiary plans and baselines, serving as the primary guide for project execution.
• Direct and Manage Project Work is where the integrated plan is executed, producing deliverables and generating performance data.
• Monitor and Control Project Work involves tracking performance against the plan, analyzing data to create information and reports, and generating change requests.
• Perform Integrated Change Control is the rigorous, formal process for reviewing, approving, and managing all changes to project baselines or plans, ensuring integrated impact analysis.
• Close Project or Phase finalizes all activities, obtains formal acceptance, documents lessons learned, and archives project information to provide organizational closure.