Skip to main content
Workforce LibreTexts

Common Mistakes and How to Prevent Them

  • Page ID
    52329
  • \( \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}\)

     

    ๐ŸŽฏ Why This Section Matters

    Even the best project plans can fall apart—not because the team lacked skills, but because they made avoidable mistakes.

    This section distills the most common missteps students (and even professionals) make during each milestone of the practicum, and offers practical advice on how to avoid them.

    Think of this as your early warning system—a checkpoint before you submit or present your work.


    ๐Ÿงฑ Milestone 1: Initiating the Project

    ❌ Mistake: Writing a generic Project Charter

    Fix: Tailor your charter to the client scenario. Use UCMS-specific context (healthcare, education, consulting) to make the goals real. Include assumptions, risks, and measurable success indicators.


    ❌ Mistake: Confusing roles or leaving them blank

    Fix: Assign functional roles (e.g., PM, QA Lead) clearly in your charter. Clarify responsibilities and align them with deliverables early on.


    ๐Ÿ—บ️ Milestone 2: Defining the Project Scope and Approach

    ❌ Mistake: Treating “Project Approach” like a narrative

    Fix: Structure this section with headers like: Scope Summary, Execution Structure, Deliverables, Architecture Overview, and Project Phasing.


    ❌ Mistake: Ignoring deliverable boundaries

    Fix: Define what is in and out of scope. If stakeholders ask for extras later, you’ll need this boundary to track scope creep.


    ๐Ÿงฎ Milestone 3: Building the Work Plan and Schedule

    ❌ Mistake: Listing tasks instead of structuring a real WBS

    Fix: Organize work hierarchically—Phase > Deliverable > Work Package. Each item should be assignable, trackable, and budgetable.


    ❌ Mistake: Underestimating task duration or effort

    Fix: Don’t guess. Use effort × rate formulas and buffer for unknowns. Cross-check duration vs. effort to catch gaps.


    ๐Ÿ’ฐ Milestone 4: Estimating Costs and Building the Budget

    ❌ Mistake: Forgetting key cost categories

    Fix: Include both labor (by role) and non-labor (tools, training, licenses). Don’t forget to add a contingency line (5–10%).


    ❌ Mistake: Submitting numbers without narrative

    Fix: Pair your budget table with a Funding Narrative that explains assumptions, rationales, and why your budget makes sense.


    ๐Ÿ“Š Milestone 5: Controlling Scope and Schedule

    ❌ Mistake: Tracking tasks but ignoring scope creep

    Fix: Use a Scope Control Register and log all changes, even “small requests.” Flag deviations from your WBS and escalate early.


    ❌ Mistake: Building dashboards no one can read

    Fix: Keep dashboards scannable—one page, clear status colors, and a summary. Don’t cram in everything. Focus on milestones, % complete, blockers, and top risks.


    ๐Ÿงพ Milestone 6: Controlling Budget and Quality

    ❌ Mistake: Ignoring variance explanations

    Fix: Budget logs show “what happened.” Variance tables explain why. Without the narrative, your numbers mean nothing.


    ❌ Mistake: Using vague quality criteria

    Fix: QA checklists must be specific: “All pages titled and spell-checked” beats “Well-formatted.” Make “acceptance” objective and reviewable.


    ❌ Mistake: Not tracking defects and rework

    Fix: Use a Defect Log. Assign owners, log dates, classify severity, and close the loop. This shows maturity and readiness.


    ๐Ÿ” Across All Milestones

    ❌ Mistake: Submitting empty templates

    Fix: Templates are tools, not boxes to check. Fill them with logic, thought, and decision-making. Show you used them to lead.


    ❌ Mistake: No connection between documents

    Fix: Your WBS, schedule, budget, QA plan, and dashboard should all reflect the same deliverables. Consistency builds trust.


    ❌ Mistake: Not thinking like a leader

    Fix: Don’t just complete the assignment. Ask:

    • Would this help my team?

    • Would this build sponsor trust?

    • Would I use this in the real world?

    If not—revise until it would.

    • Was this article helpful?