6.2: Plan of Attack

Plan of Attack: Risk Management and Control Planning

In this milestone, your team will shift from strategic design to resilience strategy. You’ve scoped, scheduled, and budgeted the project—now it’s time to test its strength.

Chapter 4 challenges you to create a comprehensive risk management framework and to define control mechanisms for each of the five pillars of project performance:

• Scope

• Schedule

• Budget

• Quality

• Team

Your goal is not just to prevent failure, but to prepare your plan to withstand and respond to change.

🎯 Key Objectives

By the end of this milestone, you should be able to:

• Identify and rank meaningful risks that could impact project execution

• Propose targeted mitigation and contingency strategies

• Define control mechanisms that monitor and maintain the integrity of your scope, schedule, budget, quality, and team cohesion

• Establish a system for monitoring the effectiveness of each control over time

• Present your strategy in a clear, structured, and stakeholder-ready format

📋 Step-by-Step Plan

1. Identify Risks

Brainstorm and document 10–15 risks that could threaten success across categories: people, process, tools, stakeholders, or external environment. Use a Risk Breakdown Structure (RBS) or affinity map to guide your thinking.

2. Assess and Score Risks

Use a 1–5 scale for both Likelihood and Impact. Multiply these scores to calculate Risk Priority. Assign a risk owner for each item.

3. Build a Risk Register

Create a structured table or spreadsheet that includes:

• Risk Description

• Category

• Likelihood

• Impact

• Priority Score

• Owner

• Mitigation Strategy

• Contingency Plan

4. Visualize with a Heat Map or Matrix

Summarize your register with a color-coded heat map or a quadrant matrix. This helps stakeholders quickly spot high-risk areas that need attention.

5 – Define Control Strategies for the 5 Pillars

In this step, your goal is to identify how your team will maintain stability across the five foundational pillars of project success: Scope, Schedule, Budget, Quality, and Team Dynamics. Each control strategy should be designed not only to detect problems but to prevent them—and to guide corrective action when risks materialize.

✅ Follow these instructions for each pillar:

1. Identify What Needs to Be Controlled

Start by clarifying what specific outcomes or behaviors must be protected for this area. For example:

• In Schedule, it's milestone completion on time.

• In Budget, it's not exceeding forecasted costs.

• In Scope, it's limiting unapproved expansion.

Ask:

“What could go wrong here?”
“What must stay consistent for this project to succeed?”

2. Design a Control Mechanism

Create 1–2 specific actions, tools, or checkpoints that your team will use to stay in control. Examples include:

• Dashboards or trackers

• Approval workflows

• Weekly review meetings

• Automated alerts or reports

• Issue logs and audit trails

The control must be:

• Visible (easy to track)

• Actionable (something you can respond to)

• Owned (assigned to someone on the team)

3. Document Monitoring Strategy

Controls are only effective if you monitor them. For each control:

• Define what metric will be reviewed

• Specify how often it will be reviewed (daily, weekly, per milestone)

• Assign who is responsible for monitoring

• Explain what happens if the control shows failure or slippage

Example:

“The schedule tracker will be reviewed weekly by the PM. Any task more than 3 days late will trigger an escalation to the core team.”

4. Connect Controls to Risk Triggers

Where relevant, link each control to the risks it helps mitigate. Show stakeholders how your controls are not just compliance tasks—they are risk absorbers.

Example:

“Our scope review checkpoint helps prevent the risk of unplanned features delaying training delivery.”

5. Review and Refine Across Pillars

Once all five areas are defined, step back and ensure:

• The control strategies are not duplicative or in conflict

• The frequency of monitoring is realistic and sustainable

• Ownership is clearly distributed across your team

Controls should act like a dashboard—not an emergency manual.

📄 Document your full control plan in a matrix format or narrative, organized by pillar. Include this in your submission alongside the risk register and heat map.

 6. Propose a Monitoring Strategy
For every control, define:

• What metric or data point signals success/failure

• How often the control is reviewed

• Who is responsible for measuring and reporting

• What happens when a control fails

7. Write a Risk and Control Narrative
Summarize your strategy in a 1–2 page write-up. Focus on:

• Your team’s philosophy toward risk and control

• The biggest risks and how you’re mitigating them

• How your controls enable the project to be proactive, not reactive

• Why this approach builds stakeholder confidence

📁 Final Deliverables

• ✅ Risk Register (Excel or Word)

• ✅ Risk Heat Map or Matrix (Excel, PowerPoint, or graphic tool)

• ✅ Control Plan covering all five pillars

• ✅ Risk and Control Narrative (Word document, 1–2 pages)

• ✅ Optional: Escalation matrix, risk dashboards, or team protocol guide