6.1: Scenario Building

Chapter Title: Control Implementation—Tracking Scope and Schedule
Milestone Focus: Designing and implementing the internal controls necessary to monitor scope adherence and schedule progress during project execution
Client: University College of Medical Sciences (UCMS)
Consulting Firm: C-Bay Inc. – Software Project Management Services (SPMS)

📨 Internal Memo

To: Project Planning Team – UCMS Account
From: Director, Project Management Office
Date: Week 3 of Planning Engagement
Subject: Building the Scope and Schedule Control System for the UCMS Clinical System Project

Team,

With the planning phase of our UCMS engagement nearing completion, it is time to prepare the control systems that will be used to manage project execution once the build phase begins.

As of today:

• The Charter has been approved

• Scope has been defined and confirmed by UCMS leadership

• Work packages have been structured through the WBS

• Sequencing, milestones, and estimates are finalized

• The project budget has been submitted for internal alignment and funding consideration

We are now entering the Control Design phase, which is essential to ensure that this meticulously planned project stays on track once execution begins.

🎯 Your Responsibility in This Milestone

Your role is to develop a control toolkit for the UCMS Clinical System implementation team that will be used to:

• Monitor which tasks and deliverables are complete, in-progress, or behind

• Identify any deviation from agreed scope or unapproved change

• Provide a simple and reliable view of schedule health and risk

• Escalate issues early enough to correct them without major disruption

• Enable weekly or biweekly reporting to UCMS leadership and stakeholders

🧰 What You Are Expected to Build

The control system must be lightweight, adaptable, and execution-ready. The specific tools you are being asked to produce include:

1. Scope Control Register
   A table or log that includes all major deliverables, their current status, approval checkpoints, and notes on any scope deviations or proposed changes

2. Schedule Progress Tracker
   A tool that maps your WBS or milestone tasks to current progress—using formats like % Complete, RAG status (Red-Amber-Green), or behind/on/ahead indicators

3. Change Escalation Protocol
   A visual or tabular model that defines what happens when issues are detected (e.g., delays, scope change, milestone slippage)—who decides, when, and how

4. Control Dashboard (Lite)
   A one-page summary showing overall project health, critical status areas, upcoming milestones, and any urgent flags

All four tools should be cohesive and professional. Together, they form the internal operating system for project control—not just for reporting, but for active leadership.

🔍 Constraints and Use Context

• UCMS has multiple departments engaged, and cross-team coordination will be complex. Control tools must simplify—not overwhelm—execution tracking

• Sponsors are demanding real-time insight into scope changes, milestone risk, and completion status

• Status updates will be shared biweekly in standing meetings. Your toolkit must support ongoing updates and visibility without requiring a complete rebuild each time

• The system must be flexible to adjust with project scale and team feedback, but also firm enough to prevent slippage going unnoticed

🧠 Planning Mindset

This is not a reporting exercise—it is a leadership practice.

The control system you design will:

• Catch problems early

• Reduce confusion during execution

• Enable smarter decision-making

• Build sponsor confidence

It is not enough to build a great plan. Projects succeed when they are actively managed, monitored, and corrected.

Your job now is to build the tools of that discipline.