HKSM

The Schedule Management Plan Scope baseline is the approved scope baseline (scope statement, WBS, and WBS dictionary) referenced in the schedule management plan to guide schedule development and control. It defines the authorized work and structure against which schedule activities are created, sequenced, estimated, and managed.

Key Points

• The scope baseline includes the approved project scope statement, WBS, and WBS dictionary.
• It anchors activity definition, estimation, and sequencing within the schedule management plan.
• It sets boundaries for what work is planned and tracked in the schedule, helping prevent scope creep.
• Schedule variances should be interpreted in context of scope stability or approved scope changes.
• Changes to the scope baseline require formal change control and may necessitate schedule rebaselining.
• The baseline is version-controlled and stored under configuration management for traceability.

Purpose

The purpose of referencing the scope baseline in the schedule management plan is to ensure the schedule reflects only approved work and to provide a clear structure for decomposing deliverables into activities. It aligns schedule methods, calendars, and measurement approaches with the defined scope.

This connection enables consistent estimation, realistic dependencies, and disciplined control when evaluating schedule impacts from scope changes.

Pre-requisites

• Approved project scope statement describing deliverables, boundaries, and acceptance criteria.
• Completed WBS with uniquely coded work packages.
• WBS dictionary entries detailing scope, assumptions, constraints, and acceptance information.
• Requirements documentation and traceability to confirm completeness of scope.
• Stakeholder alignment and formal approval of the scope baseline.

How to Set Baseline

• Decompose deliverables into a hierarchical WBS until work packages are manageable and estimable.
• Document each component in the WBS dictionary, including scope descriptions and acceptance criteria.
• Consolidate the scope statement, WBS, and WBS dictionary into a baseline package.
• Review with stakeholders for completeness, feasibility, and alignment with objectives.
• Obtain formal approval through the change control process and place under configuration management.
• Reference the approved baseline within the schedule management plan as the foundation for activity planning.

How to Use

• Define activities by decomposing each WBS work package into tasks needed to produce the deliverable.
• Sequence activities based on dependencies inherent in the WBS structure and deliverable flow.
• Estimate durations and resources by work package to maintain traceability from scope to schedule.
• Use the WBS codes to tag schedule activities, enabling roll-up reporting and control at work package levels.
• Assess schedule impacts of proposed scope changes; revise activities only after scope updates are approved.
• Monitor schedule performance at the WBS level to identify variances tied to specific deliverables.

Change Control Rules

• All changes to the scope baseline require a documented change request and governance approval.
• Evaluate schedule impacts (dates, critical path, float, resources) before approving scope changes.
• Upon approval, update the scope baseline, adjust schedule activities, and rebaseline schedule if warranted.
• Maintain version history linking each baseline change to its approved request and impact assessment.
• Communicate updates to stakeholders and update related plans (schedule management plan, performance thresholds) as needed.

Example

A project’s WBS includes WP-2.3: User Training Materials. The schedule team creates activities for content drafting, reviews, formatting, and delivery mapped to WP-2.3. When a stakeholder requests an additional training module, the team first submits a change request to update the scope baseline. Only after approval do they add new activities, adjust dependencies, and, if necessary, rebaseline the schedule.

PMP Example Question

While developing the schedule, a sponsor asks to add a new deliverable. What should the project manager do first?

1. Add the related activities to the schedule and update the scope baseline later.
2. Submit a change request to update the scope baseline before modifying the schedule.
3. Reject the request and proceed with the existing schedule baseline.
4. Update the schedule management plan to change reporting thresholds.

Correct Answer: B — Submit a change request to update the scope baseline before modifying the schedule.

Explanation: The schedule must reflect approved scope. Scope changes require formal change control; schedule activities are added only after the scope baseline is updated.