PMI PMP: Project Planning & Integration — Study Guide

By Laurynas Brazys · 21 July 2026 · #pmi #pmp #certification #exam-prep #study-guide

Part of the PMP — Study Guide. Practice with verified answers in the PMI exam hub, or take timed practice tests on ExamRoll.io.

Project Charter, Initiation & Stakeholder Alignment

The project charter is the instrument that formally authorizes a project’s existence and grants the project manager authority to apply organizational resources. Its power comes not from its length but from what it locks in: high-level objectives, measurable success criteria, a summary milestone schedule, preliminary budget, assumptions and constraints, the assigned project manager and their authority level, and the sponsor’s signature. Without a signed charter, a project manager operates on informal permission—every resource conflict, every scope dispute, every escalation becomes a negotiation from weakness.

During initiation, the project manager must convert the sponsor’s vision into shared understanding. This means holding structured conversations with the sponsor and key stakeholders to clarify why the project exists (the business case), what “done” looks like (acceptance criteria), and who has decision rights. A multimedia exhibition-design project, for example, cannot proceed to plan development until the project manager knows whether the sponsor prizes opening-night readiness (fixed date), curatorial fidelity (fixed scope), or budget discipline (fixed cost). These trade-offs shape every subsequent planning decision.

Stakeholder alignment at initiation is not a formality. Identifying stakeholders, analyzing their interests, influence, and expectations, and validating their understanding of the project’s purpose surfaces conflicts while they are cheap to resolve. A stakeholder register created early—and refined continuously—prevents the classic failure mode of discovering a powerful stakeholder mid-execution who never accepted the objectives.

WBS Decomposition and the WBS Dictionary

The Work Breakdown Structure decomposes total scope into deliverables and further into work packages. The correct level of decomposition is the level at which a work package can be reliably estimated for cost and duration, assigned to a single accountable owner, and monitored for progress. This is often called the 8/80 heuristic (work packages between roughly 8 and 80 hours of effort), but the true test is control, not hours.

Over-decomposition creates administrative overhead: hundreds of micro-tasks that consume more time to track than they take to perform, and that fragment ownership. Under-decomposition hides risk: a work package labeled “Build superstructure” on a bridge project is too coarse to estimate meaningfully, so cost and schedule contingencies balloon and variance analysis becomes impossible. For the bridge example, decomposition should continue until each package (e.g., “Fabricate south abutment rebar cage”) is discretely estimable and assignable to a foreman.

The WBS dictionary complements the WBS by defining, for each work package, the scope of work, responsible organization, schedule milestones, resource requirements, quality criteria, acceptance criteria, and technical references. It is the bridge between the visual WBS and the estimating, scheduling, and quality processes. Skipping the dictionary is a common cause of scope disputes because the WBS box alone is ambiguous.

Integration of Subsidiary Plans

The project management plan is not a document; it is an integrated set of subsidiary plans and baselines. The scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder engagement management plans must be internally consistent. If the quality plan mandates two independent test cycles but the schedule allows only one, the plan is not integrated—it is a collection of documents.

• Scope — WBS aligns with schedule activities and cost estimates
• Schedule — Resource calendars reconciled with resource management plan
• Cost — Contingency reserves reflect risk register
• Quality — Metrics feed monitoring and controlling processes
• Resources — Skills required match procurement plan for gaps
• Risk — Response strategies budgeted in cost plan, timed in schedule

The three baselines—scope, schedule, and cost—together form the performance measurement baseline. Once approved, these change only through integrated change control. Treating baselines as suggestions rather than controlled references destroys earned value analysis and undermines variance reporting.

Life-Cycle Selection and Tailoring

Selecting predictive, adaptive, or hybrid approaches is a deliberate decision driven by uncertainty of requirements, rate of change, stakeholder involvement expectations, regulatory constraints, and delivery cadence needs.

• Predictive suits projects with stable, well-understood requirements, fixed regulatory scope, and low tolerance for change (bridge construction, regulatory filings).
• Adaptive (agile) suits high-uncertainty work where requirements will emerge through use and feedback (novel software features, R&D prototypes).
• Hybrid applies when different components of the same project have different characteristics.

A long-timeline program that needs both a stable multi-year architecture and near-term deliverable features is a textbook hybrid case: the project manager sets a rolling-wave predictive framework for the overall roadmap, milestones, and infrastructure, while adaptive iterations deliver features incrementally. Governance layers accommodate both—stage-gate reviews for the predictive envelope, sprint reviews and retrospectives inside the adaptive layer.

Tailoring extends beyond life-cycle choice to ceremonies, artifacts, tools, and roles. A small internal project may need only a lightweight charter and a Kanban board; a regulated pharmaceutical project requires formal design history files regardless of iteration style.

Assumptions, Dependencies, Constraints, OPAs and Lessons Learned

Assumptions, dependencies, and constraints must be captured in an assumption log during initiation and reviewed continuously. Assumptions untested become the risks that materialize; dependencies unmapped become the schedule slips. When inheriting a project, the incoming project manager must review organizational process assets—templates, historical estimates, closed-project archives—and specifically the lessons learned repository. Failing to do so repeats predecessors’ mistakes and forfeits available templates, calibrated estimating data, and known-good vendor lists.

PMIS, Document Control, and Baselines

The Project Management Information System houses the schedule, cost, document repository, change log, and reporting tools. Version control, access permissions, and configuration management protect baseline integrity. Every approved change updates baselines through integrated change control; the prior baseline is archived, not overwritten, to preserve auditability.

Readiness Validation and Contract Alignment

Before switching approaches mid-project—or before beginning a hybrid execution—validate technical and organizational readiness. This includes verifying that team members possess required skills, that infrastructure supports the chosen cadence (CI/CD for agile, for example), and that governance bodies can operate at the required rhythm. When a multi-team project shifts approach without this validation, missing technical capability surfaces only after work has begun, forcing rework. The remedy is a readiness assessment during planning: skills inventory, tool audit, and pilot activity before broad rollout.

Contracts must align with the chosen life cycle. Firm-fixed-price contracts assume predictive, stable scope; imposing them on adaptive work forces vendors to inflate estimates or resist change. Hybrid execution typically requires time-and-materials or incentive-based structures for the adaptive components while retaining fixed price for stable deliverables.

Common Traps Explained

Launching execution without clarifying requirements and stakeholders guarantees rework because the definition of done is not shared—work is judged against expectations that were never surfaced. Over- or under-decomposing the WBS breaks estimating: too fine, and noise dominates; too coarse, and estimates are guesses. Skipping OPA and lessons-learned review on inherited projects discards institutional memory and repeats known failures. Misaligning contracts with a hybrid approach creates legal and commercial friction—vendors are contractually rewarded for behaviors incompatible with the chosen delivery model, and change requests become disputes rather than collaborations.

Practical Problem: Use-Case Scenario

Scenario: Priya Nair has just been named project manager for the “Ocean Realms” interactive exhibition at the Meridian Science Museum, a $2.4M multimedia installation slated to open in 11 months to coincide with the museum’s 50th anniversary gala. The executive sponsor verbally approved the project three weeks ago, but Priya has since discovered that the curatorial director expects six themed zones (the sponsor mentioned four), the marketing VP has already committed the opening date to major donors, and the facilities manager was never consulted about the load-bearing requirements for a planned 12-ton kinetic sculpture. No charter has been signed, and Priya has been asked to begin vendor contracts next week.

Challenge: Priya must halt the drift toward unauthorized execution and establish formal authority, aligned objectives, and clarified trade-off priorities before any procurement commitments are made.

Recommended Approach:

1. Schedule a 90-minute chartering session with the executive sponsor within five business days to explicitly rank the triple constraint — confirm whether the anniversary gala date, the curatorial scope, or the $2.4M budget is the fixed dimension.
2. Draft the project charter capturing the ranked priority, measurable success criteria (visitor throughput, exhibit uptime, opening-date readiness), a milestone-level schedule, the preliminary budget, key assumptions, and Priya’s authority to commit spend up to a defined threshold.
3. Conduct individual 30-minute alignment interviews with the curatorial director, marketing VP, facilities manager, and lead donor liaison to document their expectations, influence, and decision rights in a stakeholder register.
4. Facilitate a stakeholder alignment workshop where the sponsor personally communicates the ranked trade-offs and resolves the four-versus-six zones question and the sculpture load-bearing issue on the record.
5. Obtain the sponsor’s signature on the charter and distribute it, along with the stakeholder register, to all named stakeholders before issuing any vendor RFPs.
6. Log unresolved items (e.g., sculpture engineering feasibility) in an assumptions and constraints register for immediate follow-up during planning.

Why This Works: Locking in a signed charter with an explicit trade-off ranking gives Priya the positional authority to arbitrate the inevitable conflicts between curatorial ambition, marketing commitments, and engineering realities. It prevents the classic pitfall of racing into procurement while stakeholders hold divergent mental models of “done” — a situation that produces expensive change orders and eroded sponsor trust once contradictions surface mid-execution.

← Procurement · All domains · Governance →

Practice these questions → · Timed practice on ExamRoll.io →