7.2: Plan of Attack

 

🎯 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:

1. Budget Tracking Log or Cost Burn-down Sheet

   • Tracks how much of the budget has been used over time

   • Includes cumulative totals, category breakdowns, and visual summaries

2. Variance Analysis Table

   • Compares planned vs. actual spending by phase, role, or cost type

   • Includes variance amounts, percentage difference, and explanations

3. Narrative Flagging Mechanism

   • Highlights causes of over/under spending

   • 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:

1. QA Acceptance Checklist

   • Lists deliverables, associated quality criteria, and sign-off checkpoints

   • Defines “done,” “needs revision,” and “rejected” status for each item

2. Defect Log or Quality Tracker

   • Records reported issues, their severity, owner, and resolution path

   • Useful for stakeholder review and team accountability

3. Quality Escalation Flow (Optional)

   • Shows what happens when a quality issue cannot be resolved by the delivery team

   • 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:

1. Team Review

2. PM + Stakeholder Review

3. 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:

1. Budget Tracking Table

2. Variance Analysis Table

3. QA Acceptance Checklist

4. Defect Log or Quality Tracker

5. (Optional but recommended) Quality Escalation Flow or QA Rhythm Summary