HKSM

The scope baseline is the approved, version-controlled package that combines the project scope statement, the WBS, and the WBS dictionary. It defines the official boundaries of work and serves as the benchmark for measuring scope performance and managing changes.

Key Points

• Consists of the project scope statement, the work breakdown structure (WBS), and the WBS dictionary.
• Represents the approved definition of in-scope work and is used to measure scope performance.
• Changes to the scope baseline require formal change control and versioning.
• Supports planning, estimating, work authorization, and acceptance of deliverables.
• Helps prevent scope creep by clarifying boundaries and acceptance criteria.
• In adaptive approaches, a release or product goal may be baselined, with backlog changes governed accordingly.

Purpose

• Establish a clear, shared understanding of what is in and out of scope.
• Provide a reference to assess scope variances and impacts of proposed changes.
• Enable consistent planning and estimating across the team and vendors.
• Guide acceptance and verification of deliverables against agreed criteria.
• Support integration with schedule and cost baselines for performance measurement.

Pre-requisites

• Approved or well-understood requirements and acceptance criteria.
• Draft project scope statement capturing product and project scope boundaries.
• Decomposition approach agreed (how WBS levels and coding will be structured).
• Change control process and configuration management plan defined.
• Stakeholder roles for review and approval identified and available.
• Constraints, assumptions, and dependencies documented.
• For adaptive delivery, a stable release goal or baseline backlog for the period.

How to Set Baseline

• Refine the project scope statement to capture objectives, deliverables, inclusions, exclusions, and acceptance criteria.
• Decompose deliverables into a hierarchical WBS until work packages are manageable for planning and control.
• Create the WBS dictionary to describe each work package (scope, deliverables, criteria, constraints, and responsible party).
• Cross-check traceability from requirements to WBS elements to confirm completeness.
• Validate the scope package with key stakeholders for clarity and feasibility.
• Align the scope baseline with schedule and cost planning assumptions.
• Submit the scope statement, WBS, and WBS dictionary for formal approval.
• Record the baseline version, approval date, and configuration identifiers.

How to Use

• Authorize work only for items included in the baseline.
• Assess change requests by comparing proposed work to the baseline and analyzing impacts.
• Measure scope performance and identify variances at the work package or control account level.
• Support deliverable verification and stakeholder acceptance using the defined criteria.
• Guide estimating, resource planning, and procurement for in-scope items.
• Communicate scope boundaries to prevent gold plating and scope creep.
• Inform schedule and cost updates when scope changes are approved.

Change Control Rules

• No additions, deletions, or modifications to baseline scope without an approved change request.
• Perform impact analysis on schedule, cost, quality, risks, and benefits before approval.
• Use configuration management to version and archive each baseline update.
• Update related plans (schedule, cost, quality) when scope changes are approved.
• Maintain a change log and variance log to track decisions and rationale.
• Communicate approved changes and effective dates to all affected stakeholders.
• For adaptive approaches, apply product governance (e.g., product owner decisions) within agreed guardrails.

Example

A project to deliver a two-day professional workshop sets its scope baseline as follows:

• Scope statement: Deliver a two-day workshop with facilitator guide, participant workbook, venue setup, and post-event feedback; out of scope includes on-demand video production.
• WBS (excerpt): 1.0 Plan workshop; 2.0 Develop content; 3.0 Logistics; 4.0 Deliver event; 5.0 Close project.
• WBS dictionary (sample entry 2.2 Slide Deck): 40-slide deck with facilitator notes; acceptance criteria include accuracy, brand compliance, and peer review sign-off; owner: Lead Trainer.

When a stakeholder requests an additional breakout session, the team compares it to the baseline, estimates impacts on duration and cost, submits a change request, and only updates the baseline after formal approval.

PMP Example Question

Which artifact is part of the scope baseline used to control scope changes?

1. Requirements traceability matrix
2. Project scope statement
3. Requirements management plan
4. Stakeholder engagement plan

Correct Answer: B — Project scope statement

Explanation: The scope baseline comprises the project scope statement, the WBS, and the WBS dictionary. The other documents support scope management but are not components of the baseline.