7.2: Plan of Attack

Last updated
Save as PDF

Page ID: 52245

$ \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}$

Objective of This Milestone

The goal of this milestone is to design a live control system for two of the most scrutinized dimensions of any project:
Budget performance and deliverable quality.

In Milestones 3–5, you created detailed plans, cost models, and execution control tools. Now you must build tools to:

Track actual project spending against your planned budget
Identify and respond to financial variance
Ensure that what is delivered meets stakeholder expectations
Detect and resolve quality issues before they derail project success

This milestone transforms your project from a plan on paper into a living, accountable operation.

What You Will Build

Your final deliverable will include two integrated control systems:

PART 1: Budget Control System

Purpose:
To monitor actual project costs (labor + non-labor) in real time, and detect deviations from the budget approved in Milestone 4.

What You Will Build:

Budget Tracking Log or Cost Burn-down Sheet
1. Tracks how much of the budget has been used over time
2. Includes cumulative totals, category breakdowns, and visual summaries
Variance Analysis Table
1. Compares planned vs. actual spending by phase, role, or cost type
2. Includes variance amounts, percentage difference, and explanations
Narrative Flagging Mechanism
1. Highlights causes of over/under spending
2. Suggests resolution, reallocation, or escalation

PART 2: Quality Control & Assurance System

Purpose:
To verify that each deliverable is reviewed, meets acceptance standards, and—if not—triggers corrective action.

What You Will Build:

QA Acceptance Checklist
1. Lists deliverables, associated quality criteria, and sign-off checkpoints
2. Defines “done,” “needs revision,” and “rejected” status for each item
Defect Log or Quality Tracker
1. Records reported issues, their severity, owner, and resolution path
2. Useful for stakeholder review and team accountability
Quality Escalation Flow (Optional)
1. Shows what happens when a quality issue cannot be resolved by the delivery team
2. Includes severity-based thresholds for review or rework

Step-by-Step Execution Plan

Step 1: Reconnect to Your Approved Budget

Review your submitted budget: labor categories, unit rates, non-labor items, contingency, etc.
Identify which line items or cost categories will be tracked separately (e.g., development labor, vendor licenses, stakeholder training)
Confirm the unit of tracking: weekly cost, per role, per deliverable, or per phase

Deliverables: Budget Categories Table + Baseline Reference

Step 2: Build the Budget Tracking Log

Create a spreadsheet or table to show:
- Budgeted amount
- Actual amount spent to date
- Remaining budget
- % Burned (Actual ÷ Planned)
Organize by:
- Cost type (Labor, Tools, Travel, etc.)
- Role or task group
- Time period (weekly or phase-based)

Visuals: Use progress bars, red flags, and conditional formatting to highlight risk areas

Step 3: Create the Variance Analysis Table

Add a companion table that compares:
- Planned vs. Actual cost
- Variance ($ and %)
- Narrative explanation: "Why is this off plan?"
- Resolution notes: “Absorbed in contingency,” “Flagged to sponsor,” etc.

Tip: Track negative variance (cost savings) just as carefully as overruns

Step 4: Define QA Criteria for Key Deliverables

Select at least 3–5 client-facing deliverables (e.g., Training Deck, Workflow Spec, Pilot Build, Final Report)
Define quality criteria for each (e.g., accuracy, completeness, formatting, stakeholder sign-off)
Build a QA Acceptance Checklist with:
- Deliverable name
- Criteria
- Date submitted
- Status (Accept / Revise / Reject)
- Notes and reviewer signature

Step 5: Create a Defect Log or QA Tracker

Build a defect log table that includes:
- Defect or issue ID
- Deliverable affected
- Description
- Severity (Low/Medium/High)
- Owner
- Resolution status and date

Option: Use color coding for status (e.g., 🔴 = Unresolved, 🟡 = In Review, ✅ = Fixed)

Step 6: (Optional) Map Out a Quality Escalation Process

Define what happens when quality issues:
- Recur repeatedly
- Are blocked by reviewers
- Cannot be resolved within delivery timelines

Include a 3-tier escalation:

Team Review
PM + Stakeholder Review
Executive Review / Schedule Adjustment

Design Tips

Budget control isn’t just math—it’s pattern recognition + storytelling
Quality control is a discipline, not a checklist—design for actual usage
Use formatting that enables quick decision-making: colors, icons, filters
Make all tools execution-ready—not just formatted for grading

Submission Checklist Preview

You will submit:

Budget Tracking Table
Variance Analysis Table
QA Acceptance Checklist
Defect Log or Quality Tracker
(Optional but recommended) Quality Escalation Flow or QA Rhythm Summary

Search

Text Color

Text Size

Margin Size

Font Type