6.2.1: Step 1- Revisit Your WBS, Milestones, and Scope Map

🎯 Purpose of This Step

Before you can begin building control tools, you need to ensure you are anchored to the correct baseline.

Control systems are only effective if they measure against:

• Approved scope

• Confirmed milestones

• Structured deliverables from earlier planning stages

This step ensures you’re not building trackers “from memory” or on gut feel. Instead, you're reconnecting to what was formally planned—and possibly signed off by stakeholders.

🗂️ What You Should Gather First

Reopen the following planning assets from Milestones 2, 3, and 4:

Artifact	Purpose in This Step
Project Charter	Reminds you of scope boundaries and key deliverables
WBS (Work Breakdown Structure)	Provides the detailed hierarchy of what work is to be done
Milestone Schedule	Defines key progress checkpoints and decision gates
Scope Summary or Deliverables List	Ensures control tools are linked to the outputs that matter most
Approved Budget (Optional)	Helps align cost control logic, if you’re tracking time-bound budgets or milestone-based payments

📋 Tasks You Must Complete in This Step

🔹 1. Review the WBS in Detail

• Confirm that your Scope Control Register will include every major Level 2 or 3 deliverable or task.

• Double-check naming: the task or deliverable names in your tracker should match the WBS—no ad hoc renaming.

• Identify which tasks were marked as milestone-bound or external-facing—these often require higher control visibility.

📘 Tip:
Color-code or flag deliverables in the WBS that will be included in your control tools.

🔹 2. Map Milestones to Deliverables

• Create a reference table or mind map showing which deliverables contribute to which milestone.

• This will allow your schedule tracker and dashboard to reflect not just “tasks,” but milestone health.

• If milestones are vague (“System Ready”), define the deliverables that unlock them.

📘 Example:

Milestone	Deliverables Required
M3 – Pilot Launch Ready	Training Completed, QA Sign-Off, Pilot Build Complete
M2 – Requirements Finalized	Workflow Diagrams, User Role Mapping, Stakeholder Review Sign-Off

🔹 3. Define Your Control Baseline

Once you've verified your WBS and milestones, identify the version or snapshot that represents your official baseline plan.

This is the version against which you’ll measure all changes, slippage, or scope adjustments.

Decide:

• What counts as “planned”?

• What has been revised since? (if applicable)

• What is the cutoff date for tracking baseline vs. updates?

📘 Tip:
You can include a column in your scope register like:

Deliverable	Planned Date	Current Status	Baseline Version
QA Test Plan	Mar 10	In Progress	v3 – Signed off Mar 3

🔹 4. Reconfirm Scope Boundaries

This is your chance to tighten the edges of what will (and won’t) be tracked.

Ask:

• Are there any tasks that are out of scope but might show up in conversations?

• Is there any gray area where extra work could sneak in unnoticed?

• Do we need to document exclusions to protect the team during execution?

📘 Example:
In your Scope Control Register, you could add a field like:

Deliverable	In Scope?	Notes
Rebuild legacy reporting	No	Only migration to new platform is included

🔍 Why This Step Is Critical

Without reconnecting to your WBS and schedule:

• You may miss key deliverables that go untracked

• You risk tracking the wrong tasks or outdated versions

• Your dashboards and status tools lose credibility fast

• You’ll have no clear “source of truth” for measuring actual vs. planned

This step transforms your planning work from documentation into performance criteria. It ensures your control system is built on approved architecture, not assumptions.

✅ Outputs of This Step

By the end of this step, you should have:

1. A clean, verified list of scope items to include in the Scope Control Register

2. A mapping of deliverables to milestones, ready to inform your schedule tracker

3. A clearly defined baseline (WBS version and dates)

4. Documented exclusions or scope boundaries for edge-case clarity

5. Linked your future control tools directly to your previously approved planning assets