4.1: Scenario Building
- Page ID
- 49226
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)Title: Breaking Down the Work: Work Breakdown Structure and Initial Scheduling
Client: University College of Medical Sciences (UCMS)
Consulting Firm: C-Bay Inc. – Software Project Management Services (SPMS)
Project Phase: Planning Phase – Post-Charter
📨 Internal Memo
To: Project Planning Team – UCMS Engagement
From: Director, Project Management Office, C-Bay Inc.
Date: Week 4 of Project Timeline
Subject: Request for Work Breakdown Structure, Effort Estimation, and Initial Milestone Scheduling
Team,
With the UCMS Charter formally approved and the structural foundation of the engagement now in place, it is time to shift from strategic planning to tactical execution planning. Our client expects us to deliver more than intent—they are now asking for evidence of readiness to execute.
This milestone represents the official transition into the second half of our planning phase. Your responsibility is to define the flow of work, determine the effort required, and map out the sequencing logic of how this project will be delivered.
The goal is to translate what we've committed to—scope, deliverables, and structure—into an actionable execution model that can be used to drive the build, testing, and deployment phases.
📌 Deliverables You Are Being Asked to Produce
Your submission must include the following five components:
-
Work Breakdown Structure (WBS)
A hierarchical decomposition of the project work into structured, reviewable components. This must reflect the deliverables defined in the charter and planning documents. -
Effort and Duration Estimates
A task-level estimate of how long each activity or package will take. Provide logical, realistic ranges or effort hours, and clearly state assumptions. -
Dependency and Sequencing Map
A mapping of logical task relationships. Identify what must be done first, what can run in parallel, and what depends on external factors (e.g., stakeholder input, vendor response). -
Milestone Schedule
A set of 3–5 major delivery checkpoints with associated dates. These must be anchored in planning logic and used to structure stakeholder expectations and internal coordination. -
Planning Readiness Review
A brief review of the plan’s integrity: Are the tasks traceable to the scope? Are durations defensible? Are dependencies clear? Is the schedule consistent with the constraints?
Each of these elements must be prepared as if they will be used immediately by project team leads, reviewed by UCMS leadership, and referenced in the upcoming Phase Kickoff.
📎 Project Context
UCMS is now preparing to allocate internal resources and coordinate with external vendors. They are requesting a clear view of what work will be performed, in what sequence, and when key outcomes are expected. This means your planning package must be:
-
Usable by execution teams
-
Aligned to stakeholder availability and term cycles
-
Flexible enough to adjust as vendor input becomes available
-
Rigorously structured to maintain accountability and control
You are not being asked to produce a full project plan, budget, or resourcing document—but your work in this milestone will directly feed those next steps.
🧠Special Instructions
-
Ensure all WBS items connect back to charter-approved scope and agreed deliverables
-
Time estimates must be presented in hours or days (not weeks or vague “levels”)
-
Milestones must reflect actual decision points or major deliverable submissions
-
Dependencies should identify both hard constraints (must happen first) and soft ones (preferred order)
-
Your Planning Readiness Review is expected to highlight risks, gaps, or remaining unknowns—do not assume everything is confirmed
🎯 Intended Use
This planning package will be used to:
-
Drive the development of the Phase Execution Plan
-
Align internal teams with client milestones
-
Support UCMS decision-making and calendar planning
-
Serve as a readiness checkpoint before resource mobilization
This milestone is not academic—it’s operational. Treat it as if you are submitting it to a cross-functional delivery team ready to act on it.
We are counting on your ability to create a realistic, structured, and client-ready plan that can move this project from planning to performance.
—
Dr. Wendy Sheen
Director of Project Management Office (PMO)
C-Bay Inc