6.3: What You Will Submit
- Page ID
- 52238
\( \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}\)Purpose of This Submission
Your submission for this milestone demonstrates your team’s ability to move from planning into operational control. You are submitting a set of tools designed to:
- Monitor scope completion and milestone health
- Track actual progress against scheduled work
- Detect delays or deviations in real time
- Respond to scope creep, risks, or blockers
- Communicate status effectively to internal and external stakeholders
You are expected to submit a complete, cohesive Control Toolkit that could be used by a real project team to guide execution and reporting.
Overview of Required Components
| Component | Purpose |
|---|---|
| 1. Scope Control Register | Track all major deliverables, their completion status, and any scope change activity |
| 2. Schedule Progress Tracker | Track progress (% complete, dates, risk flags) for all critical tasks and milestones |
| 3. Change & Escalation Protocol | Provide clear rules and structure for how changes, delays, and blockers are escalated and resolved |
| 4. Control Dashboard (Lite) | One-page status summary that presents health of the project to sponsors and stakeholders |
Each component must be:
- Logically linked to your previously submitted WBS and milestone schedule
- Professionally formatted and usable in an execution context
- Clean, complete, and readable by someone who did not help build the plan
1. Scope Control Register
What to include:
- Complete list of major deliverables (Level 2/3 WBS)
- Owner or responsible party
- Original due dates
- Current status (e.g., Not Started, In Progress, Complete, Blocked)
- Percent complete (optional but recommended)
- Scope change flag (Y/N)
- Notes on scope deviations or risks
- Column to track formal approval status if needed
Submission Format:
Editable spreadsheet (.xlsx, .csv, or embedded in Word/Google Doc table)
Example Row:
| WBS ID | Deliverable | Owner | Due Date | Status | % Complete | Scope Change | Notes |
|---|---|---|---|---|---|---|---|
| 2.1.3 | Training Material Draft | Instructional Lead | Apr 5 | In Progress | 40% | No | SME review scheduled for Apr 3 |
2. Schedule Progress Tracker
What to include:
- Critical tasks, deliverables, and milestones
- Planned start and end dates
- Actual start and end dates (if known)
- Percent complete OR status indicator (RAG color or On Track / At Risk / Delayed)
- Days behind/ahead (optional)
- Short notes or blockers field
- Ownership clearly indicated
Submission Format:
- Spreadsheet or Gantt-style chart (.xlsx, .docx table, or timeline tool export)
- Optional: add progress bars, color-coding, conditional formatting for status
Example:
| Task | Owner | Planned End | Actual End | Status | % Complete | Notes |
|---|---|---|---|---|---|---|
| Finalize Requirements | BA | Mar 10 | Mar 12 | 🔴 Delayed | 100% | Approved late due to stakeholder review |
3. Change and Escalation Protocol
What to include:
- A short written procedure or flowchart outlining how issues are escalated
- Defined triggers for scope or schedule escalation
- Escalation levels (Team → PM → Sponsor)
- Table or matrix showing response timeline and decision owner
- Change Log format for tracking all raised and resolved issues
Submission Format:
- PDF, DOCX, or slide showing escalation diagram + table
- Include Change Log table with at least 1–2 mock entries
Example Change Log Entry:
| Change ID | Description | Type | Date | Owner | Impact | Status |
|---|---|---|---|---|---|---|
| SC-001 | Add security audit step to build phase | Scope | Apr 1 | PM | +12 hrs | Approved |
4. Control Dashboard
What to include:
- Project name, date, and overall status indicator
- Milestone summary with status (green/yellow/red)
- High-level progress indicators (e.g., 70% complete, 4 of 6 milestones met)
- Top 3 active risks or issues with owners
- Scope change summary or “no changes this cycle”
- Next major actions or decisions due
Submission Format:
- 1-page PDF, DOCX, or slide deck
- Designed for visual clarity: icons, tables, status bars, RAG indicators
- Should be scannable in under 60 seconds
Example Snapshot:
UCMS Clinical System – Week 6 Dashboard
Overall Status: 🟡 At Risk (Training Delay)
Milestones:
- Requirements Signed Off ✅
- Training In Progress 🟡 (2 of 4 sessions complete)
- Go-Live Prep 🔴 (Blocked by vendor access)
% Complete: 68% of WBS tasks delivered
Top Risks:
1. SME unavailable for Testing Review (Owner: QA Lead)
2. Platform license delayed (Owner: PM)
Scope Changes:
- SC-001: Audit step added, Approved Apr 1
Next Actions:
- Finish Training Sessions (Due Apr 7)
- Confirm Pilot Launch Readiness (Due Apr 10)
Submission Format Guidelines
| Requirement | Details |
|---|---|
| File Type | Submit as PDF, DOCX, XLSX, or Google Doc/Sheet link (as instructed) |
| File Name | Milestone5_ControlToolkit_TeamName.docx (or equivalent) |
| Organization | Submit as one document (preferred) or clearly labeled separate files |
| Professionalism | Clean formatting, no placeholder text, real sample data |
| Versioning | Optional: add "Week 6 Draft" or "Final Submission" tag in footer/header |
Quality Criteria for Submission
| Quality Area | What We’re Looking For |
|---|---|
| Traceability | Control tools map directly to WBS, schedule, and scope from earlier milestones |
| Clarity | Tables are readable, indicators are clear, status is not buried in long text |
| Usability | Tools are designed for actual execution—not just for the assignment |
| Completeness | All required components are present and populated with real sample data |
| Professionalism | Layout is clean, consistent; tone is sponsor-facing and execution-ready |