3.3: What You Will Submit
- Page ID
- 49236
\( \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}\)Project Initiation
Section 3: What You Will Submit – Building Your First Professional Deliverables
You’ve met with your team. You’ve clarified the challenge. You’ve begun assigning roles and sketching a work plan. Now, it’s time to create the first milestone deliverables for C-Bay leadership.
This section outlines exactly what you are expected to produce—and more importantly, what each deliverable is intended to demonstrate. These are not "busy work" assignments. These are real-world project artifacts, modeled on what professionals would submit to leadership in the first week of a real IT infrastructure project.
Deliverable 1: Project Charter
File Format: Word document
Recommended Starting Point: Example Project Charter.doc
Your team’s Project Charter is the foundational document of your practicum. It defines your project’s purpose, boundaries, and stakeholders—and provides a snapshot of your strategy at initiation.
Your Charter must include the following sections:
|
Section |
Description |
|
Project Background |
Why this project matters to C-Bay’s growth |
|
Objectives |
SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound) |
|
Scope |
What’s in and out of scope for this phase |
|
Constraints |
Budget, time, space, regulatory limits |
|
Assumptions |
What you’re assuming to proceed without perfect data |
|
Risks |
At least 3 risks with brief mitigation strategies |
|
Key Stakeholders |
Internal roles (IT Director, PM, Facilities Lead, etc.) |
|
Success Criteria |
What will define success for this milestone? |
This document should be no more than 2 pages, clear and concise, and written professionally as if it were going to the executive team.
Deliverable 2: Evaluation Matrix with Location Recommendations
File Format: Excel spreadsheet (or Google Sheets)
Recommended Template: RequirementsAnalysisFrameworkf01122013.xlsx
Your Evaluation Matrix should:
- List at least two potential locations for the new IT headquarters and data center
- Apply at least five criteria that matter to C-Bay (cost, capacity, timeline, etc.)
- Score each location using your team's scoring system (1–5, weighted criteria, etc.)
- Justify the first and second choice selections with notes or annotations
This matrix will act as your decision support tool and must be referenced in your presentation (Deliverable 4). Think of it as your evidence table.
Deliverable 3: Preliminary Cost Model
File Format: Excel or slide table
Start with a blank sheet or adapt the Budget tab in your Evaluation Matrix
You are not expected to produce a final budget. But your Preliminary Cost Model should include rough estimates for:
|
Category |
Examples |
|
Facility Costs |
Lease/rent, taxes, renovation costs |
|
Infrastructure |
Power upgrades, cooling systems, racks |
|
Server Relocation |
Transport, setup, downtime |
|
Transition Timeline |
Move-in schedule, contingency buffer |
Use basic math and clear logic. You may reference public listings or commercial averages. Be transparent about assumptions.
Deliverable 4: Team Presentation to Leadership
File Format: PowerPoint (or Google Slides)
Time Limit: 10 minutes (no more than 10 slides)
Support Tools:
- Designing Effective Slides using PowerPoint.doc
- How to Present the 100 Page Report.doc
Your presentation should:
- Begin with a clear executive summary (the bottom-line recommendation)
- Walk through your evaluation matrix and rationale
- Summarize the cost model and trade-offs
- Outline your recommended next steps
- Demonstrate professional formatting, visuals, and flow
- Include speaking roles for all team members
You may use visuals, maps, or charts—but avoid dense tables or text on slides. Let the narrative do the heavy lifting, supported by visuals.
Optional Supporting Deliverables
You may choose to include any of the following, but they are not required for this milestone:
- Stakeholder Map: Visual or tabular representation of key roles and their interests/influence
- Team Work Plan: High-level timeline, WBS, or RACI chart
- Communication Strategy Draft: Notes on how you plan to keep stakeholders informed
These deliverables will be the first entries in your Project Management Portfolio. They should reflect not only your understanding of PMBOK principles but your ability to lead through ambiguity, collaborate effectively, and present recommendations with clarity and confidence.