🔗 Integration Management
Study Notes. ClearPMPExam.com
1. What is Integration Management?
Integration Management is the glue that holds the entire project together. It ensures that all parts of the project — scope, schedule, cost, quality, risk, resources, communication — work as one coordinated whole rather than separate pieces.
Every other knowledge area (Scope, Schedule, Cost, Risk etc.) focuses on one slice of the project. Integration Management is the only knowledge area that cuts across all of them. It is the PM’s central role — making sure nothing falls between the cracks and that all decisions consider the full picture.
🏥 Real Example — Pharma App Launch
The development team wants to add a new feature (Scope). The compliance team raises a risk about regulatory approval (Risk). The client wants to move the launch date forward (Schedule). Finance flags a budget concern (Cost).
👉 Integration Management is how the PM brings all four of these conversations into one decision — evaluating the impact on the full project before approving or rejecting any change. Without integration, each team optimises for themselves and the project breaks down.
Integration Management is the only knowledge area where the PM cannot delegate authority. The PM personally owns the Project Charter, the PM Plan, and all change control decisions. Everything else can be delegated. Integration cannot.
2. The 7 Integration Processes — In Order
Integration Management has 7 processes spanning all 5 process groups. This is the highest number of processes in any single knowledge area — which tells you how important it is.
Develop Project Charter
Create the document that officially starts the project. Gives the PM formal authority to use organisational resources. Done in Initiating.
Output → Project CharterDevelop Project Management Plan
Create the master document describing how the project will be planned, executed, monitored, and closed. Integrates all subsidiary plans (scope, schedule, cost, risk etc.) into one cohesive document. Done in Planning.
Output → Project Management Plan (with all baselines and subsidiary plans)Direct and Manage Project Work
Execute the work defined in the PM Plan. Manage the team, implement approved changes, and produce project deliverables. Done in Executing.
Output → Deliverables, Work Performance Data, Change RequestsManage Project Knowledge
Use existing knowledge and create new knowledge to achieve project objectives. Capture lessons learned throughout the project — not just at the end. Done in Executing.
Output → Lessons Learned Register, Updates to Organisational Process AssetsMonitor and Control Project Work
Track, review, and report on overall project progress. Compare actual performance against the PM Plan. Identify variances and raise change requests when needed. Done in Monitoring & Controlling.
Output → Work Performance Reports, Change RequestsPerform Integrated Change Control
Review, approve, or reject all change requests. Assess the impact of every proposed change on scope, schedule, cost, quality, and risk before deciding. The Change Control Board (CCB) is involved here. Done in Monitoring & Controlling.
Output → Approved/Rejected Change Requests, Updated PM Plan and DocumentsClose Project or Phase
Formally complete the project or phase. Obtain final acceptance from the customer, close contracts, release the team, archive documents, and document final lessons learned. Done in Closing.
Output → Final Product/Service/Result, Closed Procurements, Lessons Learned, Released Resources“Develop Charter → Develop PM Plan → Direct Work → Manage Knowledge → Monitor Work → Change Control → Close” = “Dogs Don’t Do Much More Cool Catches”
3. Which Process Belongs to Which Phase
Integration is the only knowledge area that has a process in every single process group. This makes it uniquely important — the PM is integrating at every stage of the project.
4. The Project Charter — The Most Important Initiating Document
The Project Charter is the official document that formally authorises the project to begin and gives the Project Manager the authority to apply organisational resources to project activities.
Think of the Project Charter as the project’s birth certificate. Before it exists, the project doesn’t officially exist. Once it’s signed, the PM has the green light to start planning and using resources.
What Goes Inside the Project Charter
📄 Project Charter — Contents
High-level information only — no detailed plans- Project purpose and business need
- High-level project description
- High-level scope, deliverables, requirements
- High-level risks and assumptions
- High-level budget summary
- Key stakeholders and their roles
- Project sponsor name and authority
- PM name and authority level
- High-level milestones and timeline
📋 Project Management Plan — Contents
Detailed plans — created AFTER the Charter- Detailed scope statement and WBS
- Detailed schedule and timeline
- Detailed cost estimates and budget
- Quality management approach
- Resource management plan
- Communication plan
- Risk management plan
- Procurement strategy
- Stakeholder engagement plan
- All three baselines (Scope, Schedule, Cost)
Project Charter = high-level, created in Initiating, gives PM authority, written by the Sponsor.
PM Plan = detailed, created in Planning, describes HOW everything will be done, written by the PM.
Charter comes FIRST. PM Plan comes AFTER. Charter authorises the project. PM Plan describes how to run it.
Who writes the Project Charter? The Project Sponsor (or a senior manager outside the project) writes and signs it — NOT the PM. The PM is named in it but does not create it. Once signed, the PM is authorised to begin planning.
5. The Project Management Plan — The Master Document
The Project Management Plan is a comprehensive document describing how the project will be planned, executed, monitored, controlled, and closed. It integrates all subsidiary plans into one master guide.
The PM Plan is not just one document — it is a collection of 18 subsidiary plans and baselines. Every knowledge area contributes its own plan, which gets integrated into the master PM Plan. This is the integration in action.
The 18 Components of the PM Plan
Many candidates confuse the PM Plan with just a schedule or Gantt chart. The PM Plan is a collection of ALL subsidiary plans. It tells HOW the project will be managed — not just when tasks happen. The schedule is just one component inside the PM Plan.
6. Perform Integrated Change Control — The Most Tested Process
Integrated Change Control is the process of reviewing, evaluating, approving, or rejecting all change requests — and managing their impact across the entire project before implementation.
This is called integrated change control because every change must be evaluated across all knowledge areas — not just the one it seems to affect. A scope change affects schedule, cost, risk, and quality. The PM must analyse all impacts before deciding.
The Change Control Process — Step by Step
The PM must analyse the impact of the change BEFORE submitting the change request to the CCB. Never submit a change request without knowing how it affects scope, schedule, cost, and risk. The CCB needs full information to decide.
What the Change Control Board (CCB) Does
The CCB is a group of stakeholders responsible for reviewing and approving or rejecting change requests. They do not just rubber-stamp requests — they consider full project impact. On small projects, the PM may act as the CCB. On large projects, it includes the sponsor, key stakeholders, and functional managers.
Types of Change Requests: Corrective Action — fixes a deviation that has already happened. Preventive Action — prevents a future deviation. Defect Repair — fixes a faulty component. All three are identified in Monitoring & Controlling but implemented in Executing.
🏥 Real Example — Change Request in Action
A pharma client requests a new regulatory compliance module be added to their campaign portal — something not in the original scope.
Wrong approach: PM says “sure, we’ll add it” and tells the team to start building.
Correct approach: PM logs a change request → analyses impact (3 weeks extra, ₹1.5 lakh additional cost, 2 new risks) → presents full impact to CCB → CCB approves with budget increase → PM updates PM Plan → team implements the approved change.
7. Work Performance Data → Information → Reports
This three-level progression is tested frequently in the exam. The same raw numbers become more useful as they move through the project’s reporting system.
Work Performance Data
Raw, unanalysed numbers collected during execution. “Task A is 60% done.” “₹30,000 spent.” “3 defects found.”
Collected in: Executing
Work Performance Information
Data that has been analysed and compared against the plan. “CPI = 0.92 — over budget by 8%.” “SPI = 0.85 — behind schedule.”
Produced in: Monitoring & Controlling
Work Performance Reports
Formal reports communicated to stakeholders. Status reports, dashboards, forecasts presented to the sponsor and team.
Shared in: Monitoring & Controlling
Data = raw numbers (just collected). Information = analysed data (compared to plan — means something). Reports = packaged information (shared with stakeholders). Think: Raw → Cooked → Served.
“Task completed 60%” → Work Performance Data (raw). “Project is 8% over budget based on EVM” → Work Performance Information (analysed). “Monthly status report sent to sponsor” → Work Performance Report (communicated).
8. Project Management Information System (PMIS)
PMIS is software or a system used to plan, track, manage, and report on project information. It supports scheduling, cost tracking, resource management, document storage, and reporting across the project lifecycle.
Schedule Tracking
Gantt charts, milestone tracking, critical path visualisation. Keeps timeline visible to all.
Cost Tracking
Budget vs actual spend, EVM calculations, cost forecasts. Real-time financial visibility.
Resource Management
Team assignments, availability, workload tracking, and resource leveling support.
Document Storage
Central repository for all project documents — charters, plans, reports, change logs, lessons learned.
Common PMIS Tools
Microsoft Project, Jira, Asana, Trello, Smartsheet, Monday.com. In the exam, whenever you see a reference to software that manages project tracking, scheduling, or reporting — that is PMIS.
PMIS is classified as a Tool & Technique in the PMP framework — not an output. It is used across Planning, Executing, and Monitoring & Controlling. Do not confuse it with Enterprise Environmental Factors (EEF) — the Work Authorization System is part of EEF, not PMIS.
9. Lessons Learned — Not Just at the End
Lessons Learned are documented knowledge gained during the project — what went well, what went wrong, and what should be done differently in future projects.
A critical PMP concept: lessons learned are captured throughout the project — not only at the end. This is part of Manage Project Knowledge in the Executing phase. Final lessons learned are compiled and archived in the Closing phase.
📝 Lessons Learned Register
Created during Executing — living document- Captured continuously throughout the project
- Updated whenever something significant is learned
- Part of Manage Project Knowledge process
- Available to the team while work is still ongoing
📦 Final Lessons Learned
Compiled in Closing — archived for future projects- Final summary created at project close
- Archived in Organisational Process Assets (OPA)
- Available for future project teams to reference
- Part of Close Project or Phase process
Why this matters in the exam: If a question asks “when are lessons learned captured?” — the answer is throughout the project, not just at the end. If it asks “where are final lessons learned stored?” — the answer is Organisational Process Assets (OPA).
10. Assumptions and Constraints
These two concepts appear in the Project Charter and the PM Plan, and are tested in integration-related questions.
💭 Assumptions
Things believed to be true without proofFactors you accept as true for planning purposes even though you have no guarantee they are true.
Example: “The regulatory approval will be received within 4 weeks.” “The vendor will deliver on the agreed date.”
High-level assumptions → Charter. Detailed assumptions → PM Plan. If an assumption proves false → it becomes a risk.
🚧 Constraints
Restrictions that limit your optionsFixed conditions that the project must work within — non-negotiable boundaries on time, cost, scope, or resources.
Example: “Budget cannot exceed ₹15 lakh.” “Launch must happen before December 1.” “Must use existing vendor only.”
Constraints restrict planning options. The PM plans around them, not against them.
11. Quick Summary — Everything at a Glance
| Concept | One-line meaning | Exam trigger word |
|---|---|---|
| Integration Management | Ensures all project areas work together as one — PM cannot delegate this | “overall project” / “all areas working together” |
| Project Charter | Officially starts the project, gives PM authority — written by Sponsor | “authorize project” / “give PM authority” |
| Project Management Plan | Master plan describing HOW project will be run — 18 components | “plan how project will be done” / “master plan” |
| Direct and Manage Project Work | Execute work from PM Plan, produce deliverables — Executing | “doing the work” / “implementing approved changes” |
| Manage Project Knowledge | Capture lessons learned throughout project — Executing | “knowledge sharing” / “lessons during project” |
| Monitor and Control Project Work | Track overall progress, identify variances — Monitoring | “overall project performance” / “compare to baseline” |
| Perform Integrated Change Control | Review and approve/reject ALL change requests — Monitoring | “change request” / “CCB” / “approve change” |
| Close Project or Phase | Formal sign-off, archive, release team — Closing | “formal acceptance” / “close contracts” / “lessons learned at end” |
| Change Control Board (CCB) | Group that approves or rejects change requests in Traditional projects | “who approves changes” / “CCB” (Traditional only) |
| Corrective Action | Fixes a deviation that already happened — identified in Monitoring, done in Executing | “fix deviation” / “get back on track” |
| Preventive Action | Prevents a future deviation — identified in Monitoring, done in Executing | “prevent future problem” / “proactive action” |
| Work Performance Data | Raw numbers collected during Executing | “60% complete” / “₹30,000 spent” (raw facts) |
| Work Performance Information | Data analysed and compared to plan in Monitoring | “CPI is 0.92” / “behind schedule” (analysed) |
| Work Performance Reports | Formal reports communicated to stakeholders | “status report” / “report to sponsor” |
| PMIS | Software/system used to manage project information | “Microsoft Project” / “Jira” / “project software” |
| Lessons Learned Register | Living document capturing learnings throughout — Executing | “capture during project” / “ongoing lessons” |
| Assumptions | Things believed true without proof — if wrong → become a risk | “assumed that” / “believed to be true” |
| Constraints | Fixed restrictions on budget, time, or scope | “cannot exceed” / “must be done by” / “fixed budget” |
🎯 Practice Q&A — Test Yourself
Think of your answer first. Then click to reveal.
Work Performance Information = data that has been analysed and compared to the plan in Monitoring (“CPI is 0.92 — project is over budget”).
Work Performance Reports = formal reports packaged and communicated to stakeholders (“Monthly status report sent to sponsor”).
Data → analysed into Information → packaged into Reports.
✅ Integration Management complete. This knowledge area is the foundation of everything else. Every change, every decision, every document flows through Integration. Master this and the whole PMP framework clicks into place.