Directing and Managing Project Execution

Why This Matters: The Plan Is Nothing Without Execution

You can write the most elegant Project Management Plan ever conceived — a masterpiece of Gantt charts, risk registers, and stakeholder matrices. But if you cannot direct and manage the work that turns that plan into deliverables, the plan is worthless.

The execution phase is where value is created. It is where budgets are spent, teams are mobilised, and products take shape. It is also where the majority of project failures originate — not from poor planning, but from poor execution management. Scope creep silently inflates. Baselines drift unnoticed. Communications break down. The project manager who masters this phase is the one who delivers.

Core Principle: The third project phase is where all activities and tasks outlined in the Project Management Plan are executed. Monitoring and control techniques are applied by the project manager to ensure that project baselines are met and maintained.

---

What Is "Direct and Manage Project Execution"?

Direct and Manage Project Execution is the integrative process through which the project manager and team carry out the work defined in the Project Management Plan. It is not a single activity — it is the simultaneous orchestration of multiple actions across every knowledge area.

This process belongs to Project Integration Management, the discipline that ensures all project elements are properly coordinated within a single, coherent framework.

That framework incorporates three structural pillars:

• 10 Project Management Knowledge Areas (Scope, Time, Cost, Quality, HR, Communications, Risk, Procurement, Stakeholder, Integration)
• 4 Project Phases (Initiation, Planning, Execution, Closure)
• 5 Process Groups within each phase (Initiating, Planning, Executing, Monitoring & Controlling, Closing)

The PMBOK Process View

The formal PMBOK inputs, tools & techniques, and outputs for this process are critical exam knowledge:

Project Management Plan

Approved Change Requests

Enterprise Environmental Factors

Organisational Process Assets

Direct & Manage — Project Execution

Deliverables

Work Performance Data

Change Requests

PM Plan Updates

Project Document Updates

Relationship details

From	Relationship	To
Project Management Plan	leads to	Direct & Manage — Project Execution
Approved Change Requests	leads to	Direct & Manage — Project Execution
Enterprise Environmental Factors	leads to	Direct & Manage — Project Execution
Organisational Process Assets	leads to	Direct & Manage — Project Execution
Direct & Manage — Project Execution	leads to	Deliverables
Direct & Manage — Project Execution	leads to	Work Performance Data
Direct & Manage — Project Execution	leads to	Change Requests
Direct & Manage — Project Execution	leads to	PM Plan Updates
Direct & Manage — Project Execution	leads to	Project Document Updates

---

How It Works: Key Actions in Project Integration

Directing and managing execution is not about sitting back and watching progress bars fill. It demands active, continuous decision-making across nine critical action areas:

root((Direct & Manage — Project Execution

• Decisions
  • Trade-offs
  • Approvals
• People
  • Motivation
  • Conflict Resolution
• Communications
  • Stakeholder Updates
  • Team Alignment
• Controls
  • Baselines
  • Change Requests
• Problem Solving
  • Blockers
  • Escalation
• External Management
  • Politics
  • Regulations

The Project Manager's Responsibilities

During execution, the project manager wears many hats simultaneously. The formal responsibilities include:

1. Developing designs and specifications for the project
2. Preparing and managing the overall program for the project
3. Managing project communications across all stakeholder groups
4. Monitoring project issues and maintaining issue logs
5. Developing and implementing quality assurance programs
6. Preparing documentation for contracts and procurement
7. Administering contracts on behalf of the organisation
8. Undertaking liaison with external persons and agencies
9. Reporting regularly on all aspects of the project

The PM as Integrator: Notice that these responsibilities span every knowledge area — from quality to procurement, from communications to scope. This is why Integration Management exists. The PM is the single point of accountability who weaves all threads together.

---

The Integration Framework Visualised

The relationship between knowledge areas, process groups, and project phases creates a three-dimensional management space. The PM must operate across all dimensions simultaneously during execution.

Project Management Plan

Executing Process Group

Monitoring & Controlling

Deliverables

Work Performance Data

Change Requests

Relationship details

From	Relationship	To
Project Management Plan	leads to	Executing Process Group
Project Management Plan	leads to	Monitoring & Controlling
Executing Process Group	leads to	Deliverables
Executing Process Group	leads to	Work Performance Data
Monitoring & Controlling	leads to	Change Requests
Change Requests	leads to	Project Management Plan
Work Performance Data	leads to	Monitoring & Controlling

The diagram above illustrates a fundamental truth: execution and control are not sequential — they are concurrent. While the team executes work and produces deliverables, the PM is simultaneously monitoring performance data, processing change requests, and updating the plan. This feedback loop runs continuously until the project closes.

---

The Pitfalls: Where Execution Goes Wrong

Even experienced project managers fall into common traps during the execution phase:

1. The "Set and Forget" Plan The PM creates a beautiful plan during Phase 2, then treats it as a static document during execution. Plans must be living artefacts — reviewed, updated, and re-baselined as approved changes flow through.

2. Decision Paralysis When trade-offs between scope, time, and cost emerge (and they always do), indecision is more damaging than an imperfect decision. Establish clear decision-making authority and escalation paths before execution begins.

3. Ignoring Enterprise Environmental Factors Organisational culture, market conditions, regulatory requirements, and political dynamics are not abstract concepts. They are active forces that shape what your team can and cannot do. The PM who ignores them will be blindsided.

4. Communication Gaps The most common root cause of project failure is not technical — it is communication. Stakeholders who feel uninformed become stakeholders who resist. This is explored in depth in Topic 4.3.

5. Confusing Activity with Progress A busy team is not necessarily a productive team. Work performance data must be measured against baselines, not against effort expended. Earned Value Management (covered in later topics) provides the quantitative lens for this.

---

Real-World Application: Defence & Heavy Engineering Context

In heavy engineering and defence projects — shipbuilding, infrastructure, weapons systems — the execution phase often spans years and involves hundreds of contractors, subcontractors, and regulatory bodies. The principles of Direct and Manage Project Execution are amplified in these environments:

• Change requests require formal configuration management boards
• Enterprise environmental factors include export control regulations, safety standards (AS/NZS 4801), and government audit requirements
• Organisational process assets include lessons learned databases from prior multi-billion dollar programs
• Expert judgement often comes from Subject Matter Experts (SMEs) with decades of domain experience

The PM in these environments is not just a coordinator — they are the integrative leader who holds the entire program together.

Project Manager — (Integration Hub)

Integration — ⚙️

Scope — 📐

Schedule — ⏱️

Cost — 💲

Quality — ✔️

Resources — 👥

Communications — 📣

Risk — ⚠️

Procurement — 📦

Stakeholders — 🤝

Relationship details

From	Relationship	To
Project Manager — (Integration Hub)	leads to	Integration — ⚙️
Project Manager — (Integration Hub)	leads to	Scope — 📐
Project Manager — (Integration Hub)	leads to	Schedule — ⏱️
Project Manager — (Integration Hub)	leads to	Cost — 💲
Project Manager — (Integration Hub)	leads to	Quality — ✔️
Project Manager — (Integration Hub)	leads to	Resources — 👥
Project Manager — (Integration Hub)	leads to	Communications — 📣
Project Manager — (Integration Hub)	leads to	Risk — ⚠️
Project Manager — (Integration Hub)	leads to	Procurement — 📦
Project Manager — (Integration Hub)	leads to	Stakeholders — 🤝

---

Key Takeaways

• Direct and Manage Project Execution is the core process that transforms the Project Management Plan into actual deliverables.
• It belongs to Project Integration Management — the discipline that coordinates all 10 knowledge areas, 4 phases, and 5 process groups.
• The process requires simultaneous action across decision-making, conflict resolution, people management, communications, and baseline control.
• Execution and monitoring/controlling are concurrent, not sequential — the feedback loop between work performance data and plan updates runs continuously.
• The PM's formal responsibilities during execution span the entire project landscape, from quality assurance to contract administration.
• Common pitfalls include treating the plan as static, decision paralysis, ignoring environmental factors, and confusing activity with progress.

---

References:
PMBOK Guide, 5th Edition, PMI, 2013 — Chapter 4: Project Integration Management