Integration Management
The glue that holds every other knowledge area together
GanttGrind.com — Free PMP Study Guide
Overview
Integration Management is the only knowledge area that spans every other — every change request, every plan update, and every closure activity flows through it. At its core, integration management is about making trade-off decisions: when scope, schedule, cost, or quality are in conflict, the project manager uses integrated change control to evaluate requests holistically and keep the project aligned with its strategic intent.
The seven processes begin at initiation with the Project Charter — the document that formally authorizes the project and grants the PM authority to apply resources. From there, the Project Management Plan becomes the master document governing all work. During execution, the PM directs and manages project work, manages project knowledge, and processes the relentless stream of change requests through Perform Integrated Change Control, where the Change Control Board (CCB) has authority over significant changes.
Closing is often overlooked but heavily tested. Close Project or Phase requires formal acceptance, final lessons learned, archiving project documents, releasing resources, and updating organizational process assets. Projects or phases closed without formal completion leave organizations without the institutional knowledge they need for future work. The PM must close even cancelled projects following the same rigor.
Must Know at a Glance
| Term / Concept | Definition |
|---|---|
| Project Charter | Formally authorizes the project and grants the PM authority. Created by the sponsor, not the PM. |
| Project Management Plan | The master document integrating all subsidiary plans and baselines. Guides all project execution. |
| Change Request | Formal request to modify any project document, deliverable, or baseline. Must go through Perform Integrated Change Control. |
| Change Control Board (CCB) | The body responsible for reviewing and approving/rejecting change requests. The PM alone cannot approve significant changes. |
| Perform Integrated Change Control | Reviews all change requests, approves changes, manages changes to deliverables and plans. A Monitoring & Controlling process. |
| Lessons Learned Register | Living document capturing what worked and what didn't — updated continuously, not just at close. |
| Project Knowledge Management | Using existing knowledge and creating new knowledge to achieve project objectives and contribute to organizational learning. |
| Project Closure | Formal completion including final acceptance, archiving documents, releasing resources, and celebrating success. |
Process Sequence
These processes run in order — each one builds on the outputs of the previous.
- 1
Develop Project Charter
Formally authorizes the project; defines high-level requirements and constraints.
- 2
Develop Project Management Plan
Integrates all subsidiary plans into a coherent guide for project execution.
- 3
Direct and Manage Project Work
Leading and performing project work; producing deliverables and managing change requests.
- 4
Manage Project Knowledge
Using existing knowledge and creating new knowledge to achieve project objectives.
- 5
Monitor and Control Project Work
Tracking, reviewing, and reporting on overall project progress against the plan.
- 6
Perform Integrated Change Control
Reviewing change requests; approving, deferring, or rejecting changes to baselines and plans.
- 7
Close Project or Phase
Finalizing all activities, obtaining formal acceptance, and closing out the project.
Exam Strategy
How to approach these questions
Integration Management questions frequently involve change requests and the change control process. The #1 rule: all changes must go through Perform Integrated Change Control — the PM does not have authority to approve significant scope, schedule, or cost changes unilaterally. When a stakeholder verbally requests a change, the correct response is to ask them to submit a formal change request. Also remember that the PM creates the PMP with input from the team, but the sponsor approves it.
Common Mistakes
- ✕Thinking the PM can approve all changes independently — significant changes require the CCB.
- ✕Confusing the change log (list of approved/rejected changes) with change requests (not yet decided).
- ✕Assuming lessons learned are captured only at project close — they should be documented throughout.
- ✕Forgetting to close cancelled projects — even cancelled projects need formal closure.
All 25 Topics in This Domain
Click any topic for the full explanation, key points, exam tips, and FAQs.
Project Charter
A project charter is a document issued by the project sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Develop Project Charter
Develop Project Charter is the process of creating the document that formally authorizes a project or phase and documents the initial requirements that satisfy stakeholder needs and expectations.
Develop Project Management Plan
Develop Project Management Plan is the process of defining, preparing, and coordinating all plan components and consolidating them into an integrated project management plan.
Direct and Manage Project Work
Direct and Manage Project Work is the process of leading and performing the work defined in the project management plan and implementing approved changes to achieve the project objectives.
Manage Project Knowledge
Manage Project Knowledge is the process of using existing knowledge and creating new knowledge to achieve the project objectives and contribute to organizational learning.
Monitor and Control Project Work
Monitor and Control Project Work is the process of tracking, reviewing, and reporting overall project progress to meet the performance objectives defined in the project management plan.
Perform Integrated Change Control
Perform Integrated Change Control is the process of reviewing all change requests, approving or rejecting changes, managing changes to deliverables, project documents, and the project management plan, and communicating the decisions.
Close Project or Phase
Close Project or Phase is the process of finalizing all activities for the project, phase, or contract, including archiving project information, releasing resources, and completing final deliverable acceptance.
Change Control Board (CCB)
A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.
Change Requests
A change request is a formal proposal to modify any document, deliverable, or baseline on a project. Change requests include corrective actions, preventive actions, defect repairs, and updates.
Change Log
A change log is a comprehensive list of all change requests submitted during the project, along with their current status (approved, rejected, or deferred) and key details.
Configuration Management
Configuration management is the collection of procedures used to track project artifacts and monitor and control changes to these artifacts, ensuring that the description and functional characteristics of deliverables remain accurate and complete.
Lessons Learned Register
A lessons learned register is a project document used to record knowledge gained during a project so that it can be used to improve future performance on the current project and for future projects.
Lessons Learned Repository
A lessons learned repository is an organizational process asset that stores and organizes lessons learned from completed projects, making them available for use on future projects.
Project Management Information System (PMIS)
A Project Management Information System (PMIS) is an information system consisting of tools and techniques used to gather, integrate, and disseminate the outputs of project management processes.
Expert Judgment
Expert judgment is a technique that relies on the specialized knowledge and experience of individuals or groups with training, expertise, or skills in a specific area relevant to the activity being performed.
Meetings (as a Tool/Technique)
Meetings are a tool and technique used across nearly all project management processes to discuss, plan, make decisions, resolve issues, and share information among project stakeholders.
Benefits Management Plan
A benefits management plan is a document that describes how and when the benefits of a project will be delivered and the mechanisms for measuring those benefits.
Assumption Log
An assumption log is a project document used to record all assumptions and constraints identified throughout the project lifecycle.
Issue Log
An issue log is a project document used to record and monitor all issues — problems, gaps, inconsistencies, or conflicts — that arise during the project and require resolution.
Project Documents
Project documents are the collection of documents used to manage a project that are not part of the project management plan. They include logs, registers, reports, and other records that support project execution.
Project Artifacts
Project artifacts are any templates, documents, outputs, or deliverables produced during the project. They encompass all tangible and documented items created through project activities.
Business Case
A business case is a documented economic feasibility study that establishes the validity of the benefits of a selected component lacking sufficient definition and that is used as a basis for the authorization of further project management activities.
Business Documents
Business documents are documents that exist outside the project management plan and are used to make decisions about the project before it is initiated and throughout its lifecycle. They include the business case and the benefits management plan.
Transition Planning
Transition planning is the process of preparing for the handoff of the project's final product, service, or result from the project team to the customer, operations, or sustaining organization.
Related Domains
Scope Management
Defining and controlling what is (and isn't) included in the project — WBS, requirements, scope creep.
Stakeholder Management
Identifying, engaging, and managing stakeholder expectations — power grids, salience model, and engagement strategies.
PM Fundamentals & Frameworks
Core project management concepts — projects, programs, portfolios, process groups, knowledge areas, and life cycles.
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.