Welcome to the Execution Phase: Bringing the Plan to Life
Welcome to your revision notes for the Execution phase of project management! In your study of Unit A2 3: Project Management Skills and Processes for CCEA Professional Business Services, this topic represents Stage 3 of the project lifecycle.
Think of project management like baking a celebration cake. In the initiation and planning stages, you decided on the cake's design, bought the ingredients, and wrote out the step-by-step recipe. Execution is the moment you actually step into the kitchen, turn on the oven, mix the ingredients, bake the cake, and handle any unexpected kitchen mishaps along the way!
Don't worry if project management terminology feels intimidating at first. We will break down every single concept step by step so you can master your coursework portfolio and understand exactly what the examiner is looking for.
1. What is Project Execution?
Project Execution is the stage of the project lifecycle where the project management plans are enacted, planned activities and tasks are carried out, physical deliverables are produced, and team resources are coordinated to achieve the agreed client objectives.
The Role of the Project Manager during Execution
During execution, the project manager shifts from being a "planner" to an "active director and problem-solver". Their core responsibilities include:
• Directing activities: Guiding daily operations to ensure work aligns with the master plan.
• Leading the project team: Motivating members, delegating work, and fostering collaboration.
• Assigning work packages: Handing out clearly defined tasks to specific people with strict deadlines.
• Coordinating communications: Keeping both the internal team and external stakeholders fully updated.
• Tracking milestone completion: Checking that major goals are hit on schedule.
• Managing conflicts and issues: Stepping in immediately when team disagreements or operational problems occur.
Quick Key Takeaway: Planning is designing the roadmap; execution is driving the vehicle along that roadmap while steering around obstacles.
2. Implementation and Task Allocation
How does a large project actually get done without chaos? It comes down to structured breakdown and clear resource allocation.
Work Breakdown Structure (WBS) & Work Packages
During the planning phase, a Work Breakdown Structure (WBS) divides the entire project into smaller, manageable chunks. In the Execution phase, these chunks are handed out as Work Packages.
• A Work Package is a discrete bundle of work that can be assigned to an individual or a specific team.
• Each work package includes explicit deadlines, identified task dependencies (tasks that cannot start until another is finished), and assigned resources.
Resource Allocation
Execution requires deploying three vital types of resources efficiently according to your schedule and budget forecasts:
1. Human Resources: Assigning skilled team members to the tasks that suit their strengths.
2. Physical Resources: Providing necessary equipment, technology, raw materials, software, and workspaces.
3. Financial Resources: Releasing budgeted funds to pay suppliers, contractors, and day-to-day operational costs.
Memory Aid: Remember HPF — Human, Physical, Financial resources must all be in place for execution to succeed!
3. Monitoring, Tracking, and Controlling (The Triple Constraint)
Executing a project is not just doing the work; it is constantly checking that the work is being done correctly. Project managers balance the Project Control Triangle (also called the Triple Constraint): Time, Cost, and Scope/Quality.
If you change one side of the triangle, at least one other side must change too. For example, if the client wants the project finished faster (Time decreases), the Cost may rise (paying overtime) or the Scope/Quality may have to reduce.
The Three Elements of Control
• 1. Time Control: Tracking actual progress against the original baseline Gantt chart and milestone schedules. If a task runs late, the project manager must take corrective action to prevent the final deadline from slipping.
• 2. Cost Control: Monitoring the budget "burn rate" (how fast money is being spent). The manager compares actual spend versus budgeted figures to detect variances early.
• 3. Quality Control: Ensuring deliverables meet the exact client specifications and key performance standards agreed during project initiation and planning.
Scope Creep and the Formal Change Control Process
Scope Creep occurs when unauthorized tasks or client requests are gradually added to the project without extra time, money, or formal approval. This is one of the biggest reasons projects fail!
To prevent scope creep, project managers use a formal Change Control Process:
Step 1: Change Request Submission — The stakeholder or team member formally submits a written change request.
Step 2: Impact Assessment — The project manager evaluates how the proposed change impacts the triple constraints (Time, Cost, Quality).
Step 3: Approval Decision — The client or project sponsor formally approves or rejects the change, accepting any necessary adjustments to budget or deadlines.
Step 4: Plan Revision & Enactment — The project baseline plan is officially updated, and the new work package is executed.
Common Mistake to Avoid: Never assume a project manager should automatically say "yes" to a client request mid-project. Without formal change control, your project will run over budget and miss its deadline!
4. Risk Management vs. Issue Management
Examiners frequently highlight that students mix up Risks and Issues. Let's make sure you never confuse them:
• What is a Risk? A Risk is an uncertain event that may or may not happen in the future. It is managed proactively before it happens using a Risk Register and pre-planned contingency plans.
Example: "There is a risk that our supplier might deliver materials two days late."
• What is an Issue? An Issue is a problem that has already happened or is currently occurring right now during execution. It requires immediate containment, corrective action, and logging.
Example: "The supplier has not delivered the materials today, and our team cannot work."
The Issue Log & Contingency Action
When a risk becomes an active issue, it is recorded in an Issue Log. A comprehensive issue log records:
• A clear description of the problem.
• The date the issue occurred.
• The assigned owner (the person responsible for solving it).
• The corrective action taken (such as activating a contingency plan).
• The target resolution timeline and status (e.g., Open, In Progress, Resolved).
Quick Review: Risk = Future & Uncertain | Issue = Present & Certain.
5. Team Management and Stakeholder Communication
Projects are delivered by people. Even the best project plan will fail during execution if team dynamics break down or if stakeholders are kept in the dark.
Team Leadership & Performance
During execution, the project manager must actively lead their team by:
• Motivating team members: Celebrating small milestone wins and maintaining morale during high-pressure phases.
• Resolving workplace conflicts: Addressing interpersonal friction or task disputes quickly before they derail productivity.
• Conducting status review meetings: Holding regular, focused team check-ins to monitor daily progress and assign immediate priorities.
Stakeholder Communication Plans
Transparency builds trust. Project managers use structured communication methods to manage client and stakeholder expectations:
• Regular Status Reports: Providing scheduled written updates detailing completed work, upcoming tasks, and current budget status.
• Milestone Reviews: Holding formal check-ins with clients when major deliverables are reached.
• Variance Analysis: Transparently explaining any differences between planned performance and actual results, along with the corrective actions being taken.
6. Top Exam & Portfolio Pitfalls to Avoid
When compiling your Unit A2 3 portfolio or answering execution-focused questions, watch out for these four examiner-reported traps:
1. Confusing Planning with Execution:
Do not simply describe how you would draw a Gantt chart or write a budget. The execution phase is about monitoring, tracking, and controlling ongoing work in real-time against those baselines.
2. Conflating Risks and Issues:
If a scenario describes an active breakdown or unexpected staff absence occurring during the project, treat it as an issue requiring immediate corrective action, not a hypothetical risk.
3. Forgetting Change Control:
Always reference the formal 4-step change control process whenever a client asks for alterations during the build or rollout stage.
4. Lack of Contextual Application:
Avoid giving generic textbook definitions. Always apply your knowledge directly to your specific coursework scenario or client brief (e.g., specifying named team members, exact deliverables, and real-world deadlines).
Chapter Summary Checklist
Before moving on to the Project Closure phase, make sure you can confidently explain:
• The core role of the project manager during the execution stage.
• How a Work Breakdown Structure (WBS) translates into assigned Work Packages.
• How to manage the Triple Constraint (Time, Cost, Scope/Quality).
• Why Scope Creep happens and how the formal Change Control Process stops it.
• The exact difference between a Risk (future possibility) and an Issue (current reality).
• How an Issue Log is used to document and resolve real-time problems.
• How effective team leadership and stakeholder communication keep execution on track.