2.4: What You Will Submit
- Page ID
- 49211
\( \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}\)What You Will Submit
Milestone 1 Deliverable: A Professionally Written Project Charter for UCMS
Overview
Your submission for Milestone 1 is the Project Charter—a strategic, client-facing document that authorizes, defines, and aligns the work between C-Bay Inc. and its client, the University College of Medical Sciences (UCMS).
This is not an academic paper. This is your first formal act as a planning consultant. You are writing on behalf of your firm, to be read and reviewed by C-level leadership at UCMS. The document must show professionalism, clarity, and confidence.
If done well, your charter will:
- Define the boundaries and expectations of the UCMS system planning project
- Align multiple stakeholders (internal and client-facing)
- Clarify what C-Bay is being asked to do—and under what constraints
- Serve as the anchor for all future project planning work
Required Deliverables
You will submit one complete Project Charter document that includes all of the following sections:
- Project Title, Author, Date, Version – Standard business header information
- Purpose / Objective – A clear, compelling explanation of why this project is needed now—framed in UCMS’s language, not yours
- Business Context and Alignment – A strategic description of how the project supports UCMS’s mission, accreditation, curriculum operations, and institutional priorities
- Scope Overview – A short description of what the project includes and excludes. What will be defined in planning? What will not?
- Project Constraints – Identify and prioritize constraints—especially those involving timeline, cost, compliance, and scope
- Success Criteria – A list of 3–5 specific, measurable conditions that define successful delivery of this planning phase
- Stakeholders and Roles – List key names and titles (e.g., Dr. Alok Varun), with their role (Sponsor, Approver, Reviewer) and level of influence
- Risks and Assumptions – List 2–4 realistic risks and assumptions—drawn from the scenario and your reading of the SRS
- Major Deliverables / Timeline – Include at least 3 initial deliverables with target dates. You do not need to build a full schedule yet—just frame the roadmap
- Approval Table – Create a table for names, titles, signatures, and dates. This reflects C-Bay’s formal charter process
Format and Structure Requirements
To simulate a real consulting deliverable, your submission must:
- Be written in clear, client-facing language (no filler, no academic hedging)
- Be structured with headings and white space for professional readability
- Use paragraphs with narrative flow, not just bullet points
- Include tables where appropriate (e.g., stakeholders, success criteria, approvals)
- Reference specific details from the UCMS memo and SRS—this shows you’ve read deeply
- Follow the layout and prompts of the official C-Bay Project Charter Template
Evaluation Criteria
Your charter will be evaluated using the following dimensions:
- Clarity – Is the purpose obvious? Are stakeholders well defined? Are success criteria measurable?
- Strategic Thinking – Have you prioritized constraints? Identified real risks? Aligned with client goals?
- Professionalism – Does the document look like something a C-Bay consultant would submit to a Dean or CIO?
- Completeness – Are all required sections present and fully developed?
- Use of Best Practices – Have you applied the six core best practices from your milestone reference document?
Self-Review Before You Submit
Before turning in your work, ask yourself
- If I were the Dean of UCMS, would this document make me trust C-Bay?
- Can I show where I applied each best practice (purpose, constraints, success, stakeholders, risks, story)?
- Does my writing sound like a confident consultant—or a cautious student?
- Is this document ready for stakeholder approval?
What Not to Submit
- A lightly filled-in template with no context or explanation
- A “bullet dump” without narrative or transitions
- A document written in academic voice or passive tone
- A version that ignores the UCMS memo or the system SRS
- A charter that includes vague, generic language (“Deliver software to meet goals”)
Final Deliverable Snapshot
- File Format: Microsoft Word (.docx) or PDF
- File Name: UCMS_Project_Charter_[Contextname].docx
- Where to Submit: Team Deliverables Folder (or as instructed)
- Deadline: [Instructor-defined milestone date]