6.2: Plan of Attack

Objective of This Milestone

This milestone focuses on building practical control mechanisms to help project managers and delivery teams monitor execution in real time—especially around scope adherence and schedule performance.

Your job is to turn your planning assets into an active project control system that enables timely visibility, structured accountability, and responsive escalation when deviations occur.

You will design tools that allow a project manager (or project team) to answer these essential questions week after week:

• Are we on track?
• What’s done—and what’s late?
• Has anything been added or changed from scope?
• Are we managing issues before they escalate?
• How do we communicate progress effectively?

What You Will Design and Submit

Your submission will consist of a four-part Control Toolkit, built from your Milestone 3 plan and designed for immediate use in project execution.

Tool 1: Scope Control Register

This is your master tracking sheet for approved scope elements, including:

• Deliverables
• Milestone outputs
• Major work packages

You will:

• List each scope element from your WBS or milestone plan
• Assign owners, due dates, and approval checkpoints
• Track delivery status (Not Started / In Progress / Completed / Blocked)
• Note any deviation, proposed changes, or out-of-scope activity

Why it matters:
Scope creep is one of the top causes of project failure. This tool helps you see it coming and take corrective action early.

Tool 2: Schedule Progress Tracker

This tool will track each task’s or deliverable’s progress over time, linked to the milestone schedule.

You will:

• List major tasks, deliverables, or phases
• Include original start/end dates
• Track current status using a % Complete or RAG (Red/Amber/Green) system
• Highlight delays, lead time gains, or pending blockers

Options:

• Use Excel/Gantt-style formats
• Build a weekly status log
• Include conditional formatting (e.g., >5 days late = RED)

Why it matters:
Execution visibility enables proactive replanning. It prevents surprises and reduces finger-pointing.

Tool 3: Change and Escalation Protocol

You will build a simple, visual protocol for how issues or risks should be:

• Identified
• Logged
• Escalated
• Resolved

Your protocol should define:

Trigger thresholds (e.g., a task is more than 3 days behind)

• Decision owners (e.g., PM, sponsor, steering committee)
• Escalation flow (e.g., Team Lead → PM → Stakeholder)
• Frequency and format of reviews

Deliverable format:

• Escalation flowchart or table
• Risk severity matrix with escalation guidelines
• Link to communication and reporting rhythm

Why it matters:
Fast, transparent response to emerging problems keeps momentum and trust intact.

Tool 4: Control Dashboard (Lite Version)

You will build a 1-page control dashboard that provides an at-a-glance view of project health.

Minimum recommended elements:

• Project name, phase, date
• Milestone health (on track / at risk / delayed)
• Task completion summary (e.g., 12 of 20 complete)
• Top 3 issues or blockers
• Scope change log or “watch list”
• Next major milestone and dependencies

Optional visual elements:

• RAG color codes
• Bar charts
• Status icons
• Countdown timers

Why it matters:
Executives, team leads, and stakeholders rarely read long updates—but they will look at dashboards. Your design should be scannable, simple, and useful.

Step-by-Step Plan of Execution

Step 1: Revisit Your WBS, Milestones, and Scope Map

Make sure your scope register and schedule tracker tie directly to the previously approved plan.

Step 2: Create the Scope Control Register

List every major deliverable or output. Add status columns, update triggers, and change notes.

Step 3: Build the Schedule Tracker

Map key dates and link to tasks. Decide on a tracking method (RAG, % complete, task labels).

Step 4: Design Escalation and Control Logic

Create a flow that describes when and how to raise a flag—and who makes decisions.

Step 5: Summarize With a 1-Page Control Dashboard

Bring your plan together. Use formatting, clarity, and structure to design a weekly or biweekly leadership-facing tool.

Tips for Success

• Use tools that your team could actually use during execution
• Think “low lift, high value”—don’t overbuild complex trackers that will never be updated
• Remember: the best control system is the one people actually follow
• Use Excel, Notion, Google Sheets, or another simple format—make it digital, editable, and collaborative
• Ask: Would this help us detect scope creep or delay—before it’s too late?

Your Final Submission Will Include:

1. Scope Control Register (table format)
2. Schedule Progress Tracker (Gantt, % Complete, or RAG-based)
3. Change Escalation Protocol (flowchart or matrix)
4. Control Dashboard (1-page summary format)