T09: Integrate Planning | Domain 2

📖 Integration Management — The PM's Core Responsibility

🇺🇸 English

Integration management coordinates all knowledge areas and processes across the project lifecycle. The PM is the integrator — the only person who sees the whole picture.

Project Management Plan is the master document that integrates all subsidiary plans:

Scope Management Plan | Requirements Management Plan
Schedule Management Plan | Cost Management Plan
Quality Management Plan | Resource Management Plan
Communications Management Plan | Risk Management Plan
Procurement Management Plan | Stakeholder Engagement Plan

Project charter: The document that formally authorizes the project and gives the PM authority. Created BEFORE the PM plan. Signed by sponsor.

Rolling Wave Planning: Plan in waves — detail near-term, high-level future. Especially relevant for Agile and complex projects.

Reference: PMI — Integration Management

🇻🇳 Tiếng Việt

Integration management phối hợp tất cả các knowledge areas và processes xuyên suốt vòng đời dự án. PM là người tích hợp — người duy nhất thấy toàn bộ bức tranh.

Project Management Plan là tài liệu chủ tích hợp tất cả các subsidiary plans.

Project charter: Tài liệu chính thức ủy quyền dự án và trao quyền cho PM. Được tạo TRƯỚC project management plan. Ký bởi sponsor.

Rolling Wave Planning: Lập kế hoạch theo từng đợt — chi tiết gần hạn, cấp cao cho tương lai.

📋 Planning Sequence

Project Planning Flow

── INITIATING ─────────────────────────────────────────── Business Case → Why do this project? ROI, strategic alignment Project Charter → PM authorized; high-level scope, budget, schedule Signed by: SPONSOR (not PM) ── PLANNING (iterative, not linear) ──────────────────── Scope: Collect requirements → Define scope → Create WBS Schedule: Define activities → Sequence → Estimate durations → Critical path Cost: Estimate costs → Determine budget (BAC) Quality: Quality management plan, metrics, acceptance criteria Risk: Identify → Analyze → Plan responses Stakeholders: Stakeholder register → Engagement plan Communications: Who needs what, when, how Resources: Resource management plan, RACI matrix Procurement: Make/buy decisions, contracts needed ── INTEGRATION ────────────────────────────────────────── PM Plan: All subsidiary plans compiled and reviewed for consistency Baselines set: Scope + Schedule + Cost = Performance Measurement Baseline Approved by: sponsor (formal baseline) ── KEY RULE ────────────────────────────────────────────── Planning is ITERATIVE — changes to schedule may require cost re-estimate Changes to scope require updates to schedule, cost, risk, and quality plans

🗂️ Project Charter vs Project Management Plan

Aspect	Project Charter	Project Management Plan
Purpose	Authorizes the project and PM	Describes how the project will be executed, monitored, and controlled
Created by	Sponsor (with PM input)	PM (with team input)
Approved by	Sponsor / Initiating organization	Sponsor / Key stakeholders
Timing	During Initiating	During Planning
Level of detail	High-level: objectives, constraints, assumptions	Detailed: all subsidiary plans, baselines, metrics
Change process	Only changed if project fundamentally changes	Updated via change control throughout project

🎯

Exam Tips — Integration & Planning

Project Charter = PM's authority. Without it, PM has no formal power. Sponsor creates/signs it.
Planning is iterative and progressive — revisit and refine as more info becomes available
PM plan is the baseline — the approved version. All changes require formal approval.
Integration = understanding how changes in one area affect all others. This is the PM's unique value.
In Agile, the "plan" is the product roadmap + sprint planning artifacts — equally important, less formal
Rolling wave = acceptable method; not a failure to plan — it's planned incompleteness

💼 Thực chiến / Scenario

🏢

FinTech Company X — Integrated Planning for Project Alpha

Context: Project Alpha là hybrid project — core platform (predictive) + sprint-based feature delivery (agile). PM phải integrate cả hai approaches.

Integration challenge: Phase 1 (backend infrastructure) có fixed scope và hard deadline (partner contract). Phase 2 (feature sprints) có flexible scope nhưng fixed velocity.

PM Plan components created:

Scope baseline: Phase 1 features fixed in project charter; Phase 2 maintained as prioritized backlog
Schedule baseline: Phase 1 on Gantt with critical path; Phase 2 on sprint cadence with release forecast
Cost baseline: Phase 1 fixed-cost estimate; Phase 2 rolling estimate based on velocity × cost/SP
Risk plan: Integration risks identified for dependency between phases
Communication plan: Partner communication formal (weekly); team communication agile ceremonies

Key integration decision: When Phase 1 slipped 1 week (Partner API delay), PM immediately updated: schedule baseline (new dates), cost baseline (1 week resource cost), risk register (new dependency risk), and communicated to stakeholders within 24 hours. All plans updated together — not in isolation.

PMP lesson: Integration management means recognizing that no plan exists in isolation. A schedule slip has cost, resource, risk, and communication implications — the PM tracks all of them.

✏️ Practice Questions

Question 1

A new PM has been assigned to a project in progress. The FIRST document the PM should review to understand the project's authorization and high-level objectives is:

A. Project Management Plan
B. Work Breakdown Structure
C. Project Charter
D. Risk Register

✅ Answer: C — Project Charter authorizes the project, names the PM, and provides the high-level scope, objectives, key stakeholders, and constraints. It's the foundational document that establishes why the project exists and what authority the PM has. The Project Management Plan (A) provides execution detail but is less foundational than the charter. WBS (B) and Risk Register (D) are subsidiary documents.

Question 2

During project planning, the PM realizes that reducing the schedule by 2 weeks requires adding 3 contractors, which increases the budget by $30,000. This is an example of:

A. Scope creep — uncontrolled expansion of project scope
B. Gold-plating — adding features beyond what the customer requested
C. Triple constraint trade-off — improving schedule performance impacts cost
D. Risk management — mitigating a schedule risk by adding resources

✅ Answer: C — This is a classic triple constraint (Iron Triangle) trade-off: scope, time, and cost are interrelated. Compressing the schedule (time) by adding resources directly increases cost. The PM must present this trade-off to the sponsor for a decision — you can have faster delivery OR lower cost, but changing one affects the others. This is the core of integration management: understanding that plans are interdependent.

Question 3

Which document establishes the PM's authority to lead the project and spend project funds?

A. Project Management Plan
B. Project Charter
C. Work Breakdown Structure
D. Project Scope Statement

✅ Answer: B — Project Charter formally authorizes the project and names the PM, granting them the authority to apply organizational resources (including budget) to project activities. Without a Project Charter, the PM has no formal authority. The Project Management Plan (A) describes how the project will be run but does not grant authority. WBS (C) and Scope Statement (D) are planning tools, not authorization documents.

🤖 AI Tools for PMs

🤖

How AI Augments This Process

AI helps PMs draft project management plans, create planning checklists, generate project charter content, and identify planning gaps before execution begins.

Sample Claude Prompts

Project Management Plan outline generation Help me create a Project Management Plan (PMP) for my project. Project: [name and description] Methodology: [Predictive / Agile / Hybrid] Team size: [number], locations: [offices] Duration: [months] Key constraints: [budget cap / fixed deadline / compliance requirements] Stakeholder complexity: [low / medium / high] Generate a Project Management Plan outline covering: 1. Scope Management Plan (how scope is defined, validated, controlled) 2. Schedule Management Plan (methodology, tools, baseline approach) 3. Cost Management Plan (budget structure, tracking method, variance thresholds) 4. Quality Management Plan (standards, QA/QC approach, DoD) 5. Resource Management Plan (acquisition, development, team structure) 6. Communication Management Plan (stakeholder comms matrix) 7. Risk Management Plan (identification, scoring, response framework) 8. Procurement Management Plan (if vendors involved) 9. Stakeholder Engagement Plan (engagement levels, strategies) 10. Change Management Plan (CCB, request process, thresholds) For each plan: key decisions to make, key artifacts to produce, key meetings to hold.

Planning assumptions and constraints log I'm in project planning. Help me identify and document assumptions and constraints. Project: [name and brief description] What I know for certain: [known facts] What I'm assuming (but haven't confirmed): [list your assumptions] External dependencies: [regulatory approvals, partner timelines, technology availability] Fixed elements (non-negotiable): [fixed date / budget cap / team composition] Review my assumptions and constraints and: 1. Flag high-risk assumptions (likely to be wrong — what happens if they are?) 2. Convert vague assumptions into testable statements with validation methods 3. Identify hidden assumptions I may have overlooked (common for this type of project) 4. Distinguish true constraints from "soft" constraints that could be negotiated 5. Create an Assumptions Log with: Assumption, Owner, Validation method, Status, Impact if wrong

Planning completeness audit I'm about to start execution on my project. Help me audit my planning for gaps. What I have documented: [list your planning artifacts — charter, WBS, schedule, budget, risk register, etc.] Project type: [size and complexity] What I feel uncertain about: [areas where planning feels thin] Audit my planning against these dimensions: 1. Scope clarity: Is the work 100% defined? Are acceptance criteria written? 2. Schedule: Is the critical path identified? Are dependencies mapped? 3. Budget: Is the cost baseline approved? Are contingency reserves defined? 4. Risk: Are high-probability/high-impact risks responded to? 5. Stakeholders: Is everyone identified? Are resistant stakeholders being managed? 6. Team: Do people know what they're doing and when? 7. Communication: Is the stakeholder comms calendar defined? 8. Change control: Is the CCB process established before any changes arrive? Output: Planning readiness scorecard (Green/Amber/Red per dimension) with specific gaps to close.

Jira / Confluence Template

Confluence — Project Management Plan Index

── CONFLUENCE: PROJECT MANAGEMENT PLAN ────────────────── Project: [Project Alpha] | PM: [name] | Approved: [date] Version: 1.0 | Next review: [milestone or date] Status: [ ] Draft [ ] Under review [ ] Approved baseline ── PLAN COMPONENTS ─────────────────────────────────────── Scope Management Plan: [link] | Status: [approved/draft] Schedule Management Plan: [link] | Baseline date: [YYYY-MM-DD] Cost Management Plan: [link] | Budget: $[total] Quality Management Plan: [link] | DoD version: [v#] Resource Management Plan: [link] | Team size: [n] Communications Plan: [link] | Last updated: [date] Risk Management Plan: [link] | Risks registered: [count] Stakeholder Engagement Plan: [link] | Key stakeholders: [count] Change Management Plan: [link] | CCB members: [names] Procurement Plan: [link / N/A] ── KEY BASELINES ───────────────────────────────────────── Scope baseline approved: [date] | Schedule baseline: [date] | Cost baseline: [date] Changes to baselines require CCB approval. Log all changes in [change log link].

Integrate Project Planning Activities