Skip to main content
Workforce LibreTexts

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{\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 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:

    1. Integrity of Structure

      • Is the WBS complete, traceable, and appropriately granular?

      • Does the task decomposition reflect both deliverables and execution flow?

    2. Planning Logic

      • Are task sequences rational and feasible?

      • Are milestones placed where meaningful progress or handoffs occur?

    3. Estimation Maturity

      • Are time and effort estimates realistic and explained?

      • Do assumptions reflect real-world constraints?

    4. 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?

    5. 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?

     


    4.6: Instructor Notes and Grading Rubric is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.

    • Was this article helpful?