PMBOK Integration Management

Overview

The PMBOK Integration Management skill supports the elaboration of documents for the Integration Management knowledge area — the discipline that unifies, consolidates, and coordinates processes across all other knowledge areas throughout the project lifecycle. It covers the full span from initiating through closing: project charters that authorize the project and establish high-level scope, project management plans that consolidate all subsidiary plans into a coherent whole, change requests with structured impact analysis, lessons learned registers for organizational knowledge management, benefits management plans, and project closure reports that formally conclude the project or phase.

Getting Started

Upload any existing project documents (business case, feasibility study, prior project artifacts) to the workspace and activate the PMBOK Integration Management skill. The agent will ask for the project context — name, sponsor, phase, and constraints — then guide you through the appropriate document structure. Whether you’re drafting a charter to kick off a new initiative or writing a closure report to wrap up a completed phase, the output follows PMBOK-aligned sections with hierarchical numbering, explicit assumptions, and cross-references to subsidiary plans.

Example Conversation

Below is an example of a typical session drafting a project charter for a CRM implementation. The agent gathers context, structures the charter, and flags items requiring stakeholder input.

You: We need a project charter for our new CRM implementation. The sponsor is our VP of Sales, Sarah Chen. We’re replacing our legacy system with Salesforce. Budget is approximately $2.4M over 18 months. The main driver is improving sales pipeline visibility and reducing manual reporting effort by 60%.

Agent: I’ll draft the charter. A few clarifying questions:

1. What are the key success criteria beyond the 60% reporting reduction? For example: user adoption rate, data migration accuracy, go-live date?
2. Are there known constraints — regulatory, integration dependencies, or organizational change concerns?
3. Who are the key stakeholders besides the sponsor? (e.g., IT Director, Sales Operations Lead, Finance)
4. What authority level should the PM have — budget discretion threshold and team selection rights?

You: Success criteria: 90% user adoption within 3 months of go-live, 99.5% data migration accuracy, and go-live by Q3 2027. Constraints: must integrate with our ERP (SAP S/4HANA) and comply with GDPR for EU customer data. Key stakeholders: CIO Marcus Weber, Sales Ops Director Lisa Park, and IT Integration Lead Tom Rivera. PM should have authority up to $50K for individual expenditures without CCB approval.

Agent: I’ve drafted the project charter with all 11 sections. Here’s what’s included:

• Purpose & Justification — linked to strategic goal of sales pipeline modernization and 60% reporting effort reduction
• Measurable Objectives — 4 SMART goals with KPIs (adoption rate, data accuracy, reporting reduction, go-live date)
• High-Level Requirements — 8 requirements covering Salesforce configuration, SAP integration, data migration, GDPR compliance, training, and reporting dashboards
• Overall Project Risk — flagged 3 summary risks: data migration complexity, user adoption resistance, and SAP integration timeline dependency
• Summary Milestone Schedule — 6 milestones from kickoff through hypercare
• PM Authority — $50K discretionary spend, team selection within allocated headcount

One item needs your input: the charter references a business case for the $2.4M investment — do you have a formal business case document, or should I note the ROI assumptions directly in the charter?

Document Excerpt

Below is a representative excerpt from a project charter drafted with the skill.

Project Charter — Excerpt

Project Name: CRM Platform Modernization (Salesforce) Sponsoring Organization: Global Sales Division Date: 2027-01-15

1. Project Purpose & Justification

The organization’s current CRM system (legacy on-premise) lacks real-time pipeline visibility, requires significant manual effort for reporting, and cannot scale to support the planned expansion into three new markets. This project replaces the legacy system with Salesforce Enterprise Edition, directly supporting the FY2027 strategic objective of “data-driven sales operations.” The expected outcome is a 60% reduction in manual reporting effort and a single source of truth for the global sales pipeline.

2. Measurable Objectives & Success Criteria

5. Overall Project Risk

6. Summary Milestone Schedule

10. Assigned Project Manager & Authority Level

This excerpt is illustrative. Final content must reflect the specific project’s data, organizational context, and current PMBOK edition guidance.