Project Execution and Control

Learning Objectives

By the end of this page, you will be able to:

• Explain the difference between project execution and project control
• Describe the key components of execution: task assignment, resource allocation, work scheduling, monitoring, and risk handling
• Interpret basic performance metrics: Schedule Performance Index (SPI), Cost Performance Index (CPI), Earned Value (EV)
• Explain variance analysis and how it triggers corrective action
• Describe the purpose of change control
• Apply execution and control concepts to a realistic project scenario

Quick Answer

Project execution is where the plan becomes reality: tasks get assigned, resources get deployed, and the deliverables actually get built. Project control runs alongside execution, continuously comparing actual progress against the baseline plan and triggering corrective action when they diverge. The two matter together because a plan is only a prediction — execution is where that prediction meets reality, and without control, a project can drift quietly off-track for weeks before anyone notices, by which point it's far more expensive to fix.

Executing the Plan

Execution takes everything decided during planning — the WBS, schedule, and resource plan — and turns it into actual work. It has five key components:

1. Task Assignment — Allocating specific work items to team members, so everyone knows exactly what they're responsible for.
2. Resource Allocation — Assigning available people, equipment, and materials to tasks based on priority and availability.
3. Work Scheduling — Following (and adjusting) the timeline created during planning as tasks actually get worked.
4. Monitoring Progress — Regularly checking status against the plan through status meetings and reporting.
5. Risk Management — Continuing to watch for and respond to risks identified (or newly discovered) during execution.

Real-world example: In a software project, the project manager assigns backend development to one developer, UI design to another, and testing to a third. Each week, the team reports progress; if the backend developer hits an unforeseen technical challenge and falls behind, the project manager can reallocate resources or adjust the schedule rather than waiting for the delay to show up at the final deadline.

Common misunderstanding: Students sometimes think execution is just "doing the work," treating it as separate from planning. In reality, execution constantly feeds information back into planning — if a task takes longer than estimated, the schedule for downstream tasks needs to be revised, not just noted and ignored.

Controlling the Project

Where execution is about doing the work, control is about measuring whether the work is going as planned and correcting course when it isn't. Its components are:

• Performance Measurement — Evaluating progress against established metrics.
• Variance Analysis — Comparing planned performance to actual performance to identify discrepancies and their causes.
• Change Control — Managing any proposed changes to scope, schedule, or budget through a formal review and approval process.
• Reporting and Communication — Keeping stakeholders informed of status, risks, and issues.

Why it matters: Without formal control, a project manager only finds out about problems when they become impossible to ignore — a missed deadline, an exhausted budget. Control is what surfaces small variances early, while they're still cheap to correct.

Performance Metrics: SPI, CPI, and Earned Value

These three metrics come from earned value management, a technique for objectively measuring how a project is really doing, not just how it feels:

• Earned Value (EV) — The value of the work actually completed so far, measured in budgeted terms (e.g., if 40% of a $100,000 project's scope is done, EV = $40,000, regardless of what was actually spent).
• Schedule Performance Index (SPI) — EV divided by Planned Value (the value of work that should have been done by now). SPI below 1.0 means the project is behind schedule; above 1.0 means ahead.
• Cost Performance Index (CPI) — EV divided by Actual Cost spent so far. CPI below 1.0 means the project is spending more than the work delivered is worth (over budget); above 1.0 means under budget.

Real-world example: If a project has earned $40,000 of value but the plan called for $50,000 of value by this point, SPI = 40/50 = 0.8 — the project is running at 80% of planned pace, a clear signal to investigate before the gap widens.

Common misunderstanding: Students often think "we're on budget" means the project is healthy. A project can be perfectly on budget while being badly behind schedule (low SPI, CPI near 1.0) — the two metrics measure different things and must be checked separately.

Variance Analysis and Change Control

Variance analysis compares what actually happened to what the plan said should happen, then digs into why. If actual cost exceeds budgeted cost, the project manager investigates: was it a bad estimate, an unforeseen risk, or scope creep? The answer determines the corrective action.

Change control is the formal process for evaluating and approving any change to the project's baseline — scope, schedule, or budget. If a client requests a new feature mid-project, change control ensures the impact on timeline and cost is assessed and explicitly approved before the change is made, rather than quietly absorbed and discovered as a surprise overrun later.

Real-world example: A client asks for two additional features on a software build. The project manager runs the request through change control: estimating the added time and cost, presenting it to the sponsor, and only proceeding once it's formally approved and the baseline is updated. Skipping this step is exactly how scope creep erodes a project's schedule and budget without anyone officially deciding to let it happen.

Key Terms

Term	Definition
Execution	The process of carrying out planned activities to produce the project's deliverables.
Control	The ongoing process of measuring project performance against the plan and correcting deviations.
Earned Value (EV)	The budgeted value of work actually completed to date.
Planned Value (PV)	The budgeted value of work that was scheduled to be completed by a given point in time.
Actual Cost (AC)	The real cost incurred for work completed to date.
Schedule Performance Index (SPI)	EV ÷ PV; measures schedule efficiency (below 1.0 = behind schedule).
Cost Performance Index (CPI)	EV ÷ AC; measures cost efficiency (below 1.0 = over budget).
Variance Analysis	Comparing planned versus actual performance to identify and explain discrepancies.
Change Control	The formal process for reviewing, approving, and documenting changes to a project's baseline.
Status Report	A regular communication to stakeholders on progress, risks, and issues.

Common Mistakes

Misconception 1: "Being on budget means the project is on track." Why it's wrong: Cost and schedule are separate dimensions of performance; a project can spend exactly what was planned while still being weeks behind. Correct explanation: Check SPI (schedule) and CPI (cost) independently — both need to be near or above 1.0 for the project to be genuinely healthy.

Misconception 2: "Change control is just bureaucratic paperwork that slows the team down." Why it's wrong: Without it, scope quietly expands and nobody has explicitly agreed to the added time or cost, which is a leading cause of project overruns. Correct explanation: Change control makes the trade-off visible and gets it approved by the people accountable for schedule and budget, before the change is made rather than after the damage is done.

Misconception 3: "Monitoring progress means waiting for the final deadline to see if the project succeeded." Why it's wrong: This defeats the purpose of control, which is to catch and correct deviations early while they're still small and cheap to fix. Correct explanation: Monitoring is continuous — regular status meetings, performance measurement, and variance analysis happen throughout execution, not just at the end.

Comparison and Connections

Aspect	Execution	Control
Focus	Doing the planned work	Measuring and correcting deviations from the plan
Key activities	Task assignment, resource allocation, work scheduling	Performance measurement, variance analysis, change control
Question answered	"Is the work getting done?"	"Is the work going according to plan, and if not, why?"

Metric	Formula	Below 1.0 Means
SPI	EV ÷ PV	Behind schedule
CPI	EV ÷ AC	Over budget

Practice Questions

Recall

1. List the five components of project execution described on this page. Answer guidance: Task assignment, resource allocation, work scheduling, monitoring progress, risk management.
2. What do SPI and CPI each measure, and what does a value below 1.0 indicate in each case? Answer guidance: SPI measures schedule efficiency (below 1.0 = behind schedule); CPI measures cost efficiency (below 1.0 = over budget).

Understanding 3. Explain why a project can have CPI near 1.0 but still be in serious trouble. Answer guidance: CPI only reflects cost efficiency; the project could be significantly behind schedule (low SPI) or facing unresolved risks and quality issues that CPI doesn't capture — being "on budget" is not the same as being healthy overall. 4. Why is change control necessary even when a requested change seems small? Answer guidance: Small changes accumulate (scope creep), and without a formal review, nobody has assessed the cumulative impact on schedule and cost or gotten sponsor approval — the process exists to make even small trade-offs visible and deliberate.

Application 5. A project has a Planned Value of $60,000 and an Earned Value of $45,000 at the midpoint check. Calculate SPI and interpret what it means for the project manager. Answer guidance: SPI = 45/60 = 0.75 — the project is running at 75% of planned pace and is behind schedule; the project manager should investigate causes and consider corrective action such as reallocating resources to critical-path tasks. 6. A client asks a software vendor to add a new reporting feature mid-project. Walk through how change control should handle this request. Answer guidance: The request should be logged, its impact on schedule and cost estimated, the sponsor/client informed of the trade-off, and formal approval obtained before development starts — only after approval should the baseline be updated to include the new feature.

Analysis 7. Compare a project that is over budget with low CPI versus one that is under budget with low SPI. Which is more concerning, and why might the answer depend on context? Answer guidance: There's no universal answer — a project team should analyze both: an over-budget project spending money it doesn't have is a financial risk; a behind-schedule project risks missing a critical deadline (e.g., a regulatory date) regardless of cost. The strong analysis explains that severity depends on which constraint (cost or time) is less flexible for that specific project. 8. A project manager skips weekly status reporting because "there's nothing new to report." Analyze the risk in this decision. Answer guidance: Skipping reporting removes the regular checkpoint where variances would normally surface; problems can compound silently, and stakeholders lose visibility, eroding trust and delaying the moment corrective action is triggered — "nothing new" is itself information that should be reported, not a reason to stop reporting.

FAQ

What's the difference between monitoring and control? Monitoring is the act of collecting information on performance (status updates, metrics); control is the decision-making layer that acts on that information — investigating variances and approving corrective action or changes.

Do small projects need earned value metrics like SPI and CPI? Not necessarily in full formality, but the underlying idea — comparing planned progress and spend to actual — scales down easily. A small project might track it with a simple spreadsheet rather than formal earned value software.

Who approves a change request? Typically the project sponsor or a designated change control board, especially if the change affects the approved budget or timeline significantly — the project manager assesses impact but usually isn't the sole approver for major changes.

Can a project be behind schedule but still finish on the original deadline? Yes, if corrective action (adding resources to critical-path tasks, cutting non-essential scope, working overtime) successfully recovers the lost time — this is exactly why catching schedule variance early through control matters.

Why does risk management appear in both execution and earlier planning? Because risk isn't a one-time planning exercise — new risks emerge and known risks change probability as work actually happens, so execution and control must keep tracking and responding to risk continuously.

Quick Revision

• Execution = doing the planned work; control = measuring and correcting against the plan.
• Five execution components: task assignment, resource allocation, work scheduling, monitoring, risk management.
• Earned Value (EV) = budgeted value of work actually completed.
• SPI = EV ÷ PV (schedule efficiency); CPI = EV ÷ AC (cost efficiency); below 1.0 is unfavorable in both.
• Being on budget (CPI ≈ 1) does not mean being on schedule (SPI could still be low), and vice versa.
• Variance analysis explains why actual performance differs from planned performance.
• Change control formally evaluates and approves changes to scope, schedule, or budget before they happen.
• Skipping change control is a common route to scope creep.
• Status reporting keeps stakeholders informed and should happen continuously, not just at project end.
• Exam tip: if given PV, EV, and AC numbers, expect to calculate and interpret SPI/CPI, not just define them.

Related Topics

Prerequisites: Project Planning and Scheduling and Risk Management in Projects — execution and control measure performance against the baseline and risk plan created there.

Related: Earned value management in depth; stakeholder communication during execution.

Next: Project Closure — how a project formally ends once execution and control confirm the work is complete.