4.6: Instructor Notes and Grading Rubric
- Page ID
- 49231
\( \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{\ket}[1]{\left| #1 \right>}\)
\(\newcommand{\bra}[1]{\left< #1 \right|}\)
\(\newcommand{\braket}[2]{\left< #1 \vphantom{#2} \right| \left. #2 \vphantom{#1} \right>}\)
\(\newcommand{\braopket}[3]{\left< #1 \vphantom{#2}\vphantom{#3} \right| #2 \vphantom{#1}\vphantom{#3} \left| #3 \vphantom{#1}\vphantom{#2} \right>}\)
\(\newcommand{\qmvec}[1]{\mathbf{\vec{#1}}}\)
\(\newcommand{\op}[1]{\hat{\mathbf{#1}}}\)
\(\newcommand{\expect}[1]{\langle #1 \rangle}\)
\(\newcommand{\dfn}[1]{\emph{\textbf{#1}}}\)
Purpose of ThiSs Milestone (Instructor Perspective)
Milestone 3 represents a pivotal transition in the practicum. It challenges students to evolve from strategic thinkers to execution planners.
Where Milestone 2 focused on structure and alignment, this chapter demands:
- Clear task decomposition
- Rational and defendable time and effort estimates
- Logical sequencing of work
- Stakeholder-centered milestone design
- A planning package that could be handed off to a real-world delivery team
This milestone helps students:
- Practice operational realism
- Move beyond checklists and templates
- Design for clarity, flow, and accountability
- Integrate technical and team perspectives into one cohesive plan
Instructor Guidance
When reviewing submissions, focus on these five lenses:
- Integrity of Structure
- Is the WBS complete, traceable, and appropriately granular?
- Does the task decomposition reflect both deliverables and execution flow?
- Planning Logic
- Are task sequences rational and feasible?
- Are milestones placed where meaningful progress or handoffs occur?
- Estimation Maturity
- Are time and effort estimates realistic and explained?
- Do assumptions reflect real-world constraints?
- Execution Readiness
- Could a team use this plan as a foundation for resource allocation and kickoff?
- Are risks, blockers, or unknowns acknowledged in the Planning Readiness Review?
- Professional Presentation
- Is the submission client-ready in tone, format, and clarity?
- Is the documentation scannable and usable by someone outside the team?
Grading Rubric (Total: 100 Points)
| Section | Criteria | Points |
|---|---|---|
| Section 1: Work Breakdown Structure (WBS) | Task hierarchy is clear, complete, and aligned to deliverables; tasks are actionable and logically grouped | 20 pts |
| Section 2: Dependencies and Sequencing | Each task has logical relationships; flow supports delivery model; external dependencies flagged | 15 pts |
| Section 3: Effort and Duration Estimation | Estimates are realistic, reasoned, and clearly documented with assumptions | 15 pts |
| Section 4: Milestone Schedule | Milestones are meaningful, well-placed, and align with stakeholder engagement | 15 pts |
| Section 5: Planning Readiness Review | Internal consistency confirmed; open risks and assumptions surfaced transparently | 15 pts |
| Execution Readiness & Coherence | Plan could realistically guide a delivery team or be handed off to stakeholders | 10 pts |
| Professionalism & Communication | Tone, structure, formatting, and documentation are client-facing and scannable | 10 pts |
Grading Scale
| Score Range | Grade | Descriptor |
|---|---|---|
| 90–100 | A | Outstanding. Professional-grade planning package suitable for real execution. Clear structure, strong logic, and defensible thinking. |
| 80–89 | B | Strong planning. Mostly consistent and well-aligned; may include minor gaps or formatting issues. |
| 70–79 | C | Basic completion. Key elements are present but may lack realism, alignment, or readiness for use. |
| 60–69 | D | Incomplete or underdeveloped. Missing structure, low clarity, or major logic flaws. |
| Below 60 | F | Not functional as a planning document. Cannot support delivery or be reviewed meaningfully. |
Feedback Prompts (For Instructor Comments)
Use the following language when writing coaching-based feedback:
- “Consider revisiting the sequencing logic—could any tasks run concurrently?”
- “Milestones are clear, but consider adding a note on stakeholder involvement.”
- “Estimates feel conservative—can you add assumptions to justify them?”
- “Strong WBS structure—can you clarify how external dependencies are managed?”
- “Planning review shows leadership—excellent attention to gaps and unknowns.”
- “Try formatting your tables to make scanning easier for a real delivery lead.”
Instructor Tips for In-Class Facilitation or Review Sessions
- Have students peer-review each other’s WBS or sequencing maps and identify improvement opportunities
- Conduct a group workshop on defending effort estimates with logic and constraints
- Ask students to “pitch” their milestone schedule to a mock sponsor or executive panel
- Use the Planning Readiness Review as a discussion tool: what would you change if this plan went live?


