100%

Module 1 - Program & Project Management

Day 3: Project Management Plan & Charter

19% of the exam - about 2.5 hours - 14 practice questions

0:00 / --:--

Reading

A Project Management Plan (PMP) is the CM's master document. It defines how the project will be executed, monitored, and controlled. On the CCM exam, expect questions asking you to identify what belongs in a PMP versus other documents, like a schedule or a budget standing alone.

Not to be confused with: if you're also taking this site's PMP course, that's a different PMP, Project Management Professional, PMI's certification. Same three letters, unrelated meanings; this lesson's PMP is always the Project Management Plan document.

The Project Charter: authorization, not planning

The charter comes first and does one job: it formally authorizes the project and names the CM's authority level. It states objectives, a scope summary, and who can commit resources and make binding decisions on the owner's behalf. Without a charter, the CM's authority is not formally established, a subtle but commonly tested point. The charter is typically issued by the owner or sponsor and works alongside the owner-CM agreement, which sets out the authority delegated to the CM. In practice, an unauthorized CM has to escalate every decision, which is exactly the inefficiency the charter exists to prevent.

The charter is not one of the PMP's subsidiary plans. It precedes the PMP and authorizes it. Treat these as two separate documents doing two separate jobs: the charter authorizes, the PMP plans execution. The exact list of subsidiary plans varies by owner and framework; this course uses these eight as its working list.

The nine governance documents at a glance

  • Project Charter (precedes and authorizes the PMP): Formal authorization of the project; states objectives, scope summary, and the CM's authority level.
  • Scope Management Plan: How scope will be defined, verified, and controlled, including a Work Breakdown Structure (WBS).
  • Schedule Management Plan: Methodology (typically CPM, Critical Path Method), update frequency, and baseline control process.
  • Cost Management Plan: Estimating basis, budget structure, cost control and reporting procedures.
  • Quality Management Plan: Quality standards, inspection and testing protocols, and acceptance criteria.
  • Communications Management Plan: Who gets what information, how often, and through what channel.
  • Risk Management Plan: How risks will be identified, assessed, and responded to (expanded fully in Module 7).
  • Procurement Management Plan: Contracting strategy, prequalification approach, and bid or award process.
  • Stakeholder Management Plan: Identifies stakeholders and defines engagement strategy (expanded in Day 5).

Exam tip: a charter authorizes; a PMP plans execution. If a question describes a document that grants the CM authority to spend project funds and commit resources, that's the charter. If it describes how that spending will be tracked, that's the Cost Management Plan.

Charter authorizes the PMP; the PMP's eight subsidiary plans The Project Charter authorizes the project and sets the CM's authority, as a separate document that precedes the Project Management Plan. The PMP itself contains eight subsidiary plans: scope, schedule, cost, quality, communications, risk, procurement, and stakeholder management. Project Charter authorizes Project Management Plan (PMP) Scope (WBS) Schedule (CPM) Cost Quality Communications Risk Procurement Stakeholder Exam trap: authorization (charter) vs. execution planning (PMP) are tested as two separate documents, not one.
The charter authorizes the project; the PMP that follows organizes the eight subsidiary plans an exam question may ask you to sort a scenario into.

The PMP is integrated, not eight independent silos

A scenario question sometimes describes a change that looks like it belongs to one plan, but actually forces updates across several. A schedule acceleration decision (Schedule Management Plan) usually changes crew size and equipment costs (Cost Management Plan), which can change safety exposure and inspection sequencing (Quality Management Plan). The exam rewards recognizing that a single decision can require coordinated updates across the PMP, not treating each subsidiary plan as if it existed in isolation.

Baselines and integrated change control

Once the scope, schedule, and cost plans are approved, they become baselines: the fixed reference points performance is measured against. A baseline does not mean frozen forever. It means any change follows a formal path rather than an informal one: a change request is submitted, its impact on scope, schedule, cost, and quality is analyzed together, an authorized party approves or rejects it, and only then is the baseline formally revised. Skipping this path, even to accommodate a well-intentioned field fix, is exactly the kind of shortcut the exam tests as the wrong answer.

The integrated change control loop A four-step loop: a change request is submitted, its impact across scope, schedule, cost, and quality is analyzed, an authorized party approves or rejects it, and only an approved change updates the baseline. Change request submitted Impact analysis scope, schedule, cost, quality Approve / reject authorized party decides Baseline updated, if approved
Only an approved change updates the baseline. A field fix made outside this loop, however reasonable, is the process failure the exam is checking for.

Progressive elaboration: the PMP is not finished at Day 3

The version of the PMP created early in Pre-Design or early Design is intentionally less detailed than the version in place by Construction. Progressive elaboration means the plan is refined in successive iterations as more accurate and complete information becomes available, without abandoning discipline or losing the baseline history. A scenario that shows a CM adding detail to the Cost Management Plan as design milestones are reached is not evidence of poor planning; it is the plan working as intended.

Why this matters for the exam

Charter-versus-PMP and baseline-versus-change-control are two of the most reliable "sort the scenario" question types in this domain. Anchor on two questions: does this document authorize, or does it plan execution? And is this change happening inside the formal control loop, or outside it?

Practice Questions

1. Which document formally establishes the CM's authority level on a project?

  1. The RFI log
  2. The Project Charter
  3. The approved baseline schedule
  4. The punch list

2. A Work Breakdown Structure (WBS) is primarily a tool of the:

  1. Scope Management Plan
  2. Risk Management Plan
  3. Quality Management Plan
  4. Communications Management Plan

3. CPM stands for:

  1. Cost Performance Metric
  2. Critical Path Method
  3. Contract Procurement Model
  4. Construction Phase Milestone

4. Which PMP component defines who receives what project information, how often, and by what channel?

  1. Cost Management Plan
  2. Procurement Management Plan, including the bid and award process
  3. Communications Management Plan
  4. Quality Management Plan

5. Without a formal charter, what is true of the CM's authority?

  1. It is not formally established
  2. It defaults to full authority over the owner
  3. It transfers automatically to the architect
  4. It is set by the contractor

6. Which plan governs inspection and testing protocols and acceptance criteria?

  1. Risk Management Plan
  2. Stakeholder Management Plan
  3. Scope Management Plan
  4. Quality Management Plan

7. A subcomponent describing contracting strategy and the prequalification approach belongs to:

  1. Cost Management Plan
  2. Procurement Management Plan
  3. Schedule Management Plan
  4. Communications Management Plan

8. A baseline is best defined as:

  1. The approved reference version of scope, schedule, or cost used to measure performance and variance
  2. A synonym for the Project Charter
  3. An informal estimate made before Pre-Design
  4. A document that can never be changed under any circumstance

9. A field team implements a scope change immediately because it seems obviously reasonable, without submitting a change request. This is:

  1. Only a problem if the change adds cost, since schedule and quality impacts do not need approval
  2. Acceptable as long as the owner finds out eventually
  3. Correct, since obviously reasonable changes don't need approval
  4. A process failure, since it bypasses impact analysis and formal approval

10. Which best describes why the PMP's subsidiary plans should be treated as integrated rather than independent?

  1. Only the Cost Management Plan ever needs updating, because cost is the one plan that changes after baseline approval
  2. Integration only matters after Construction begins
  3. They aren't related; each plan is self-contained
  4. A single decision, like accelerating the schedule, can require coordinated updates across cost, quality, and other plans

11. Progressive elaboration means:

  1. Each subsidiary plan is written once and never revisited
  2. The plan is deliberately vague forever
  3. The plan is refined in successive iterations as more accurate information becomes available, without abandoning the baseline history
  4. Only the charter can ever be updated

12. A scenario describes a document that grants the CM authority to spend project funds and commit resources. This is:

  1. The Risk Management Plan
  2. The Cost Management Plan
  3. The Project Charter
  4. The Communications Management Plan

13. The four steps of the integrated change control loop, in order, are:

  1. Update the baseline, submit the request, approve it informally, then analyze impact
  2. There is no fixed order
  3. Approve, analyze, request, update
  4. Request, analyze impact, approve or reject, update baseline

14. Which of the following is NOT one of the PMP's subsidiary plans?

  1. Stakeholder Management Plan
  2. Quality Management Plan
  3. Project Charter
  4. Procurement Management Plan

Micro-Assignment

Using the Day 1 delivery-method scenario you wrote, draft a one-page PMP outline for that project: list the charter plus all 8 subsidiary plans and write one sentence under each stating what it would specifically cover for your scenario. Then write one sentence describing a plausible field change and trace it through the four-step change control loop. This becomes the seed of a reusable field-tools notebook.

Glossary

Project Charter
Document formally authorizing the project and the CM's authority; precedes and is separate from the PMP.
WBS (Work Breakdown Structure)
Hierarchical decomposition of total project scope into manageable work packages.
Baseline
The approved version of a schedule, budget, or scope used to measure performance and variance.
Integrated change control
The formal process of submitting, analyzing, approving or rejecting, and only then incorporating a change into the baseline.
Progressive elaboration
Refining a plan in successive iterations as more accurate and detailed information becomes available.
Change request
A formal proposal to modify a document, deliverable, or baseline, submitted for impact analysis and approval.
Subsidiary plan
Any of the component plans (scope, schedule, cost, quality, communications, risk, procurement, stakeholder) that together make up the PMP.

Progress

Previous: Day 2 Next: Day 4