Monitoring and Controlling Project Work

Monitoring and controlling project work is the process of regularly comparing what is actually happening in a project against what was planned. Think of it as the 'check' part of the Plan-Do-Check-Act cycle. Its purpose is to identify any variances (differences) from the plan, analyse their causes, and decide if corrective action is needed. This is not a one-time event at the end of the project. It happens continuously throughout the project lifecycle.

A key tool in this process is variance analysis. This is the technique of quantifying the difference between the planned value (what you expected to spend or achieve by a certain point) and the actual value (what you really spent or achieved). For example, if your plan said you would complete 50% of the work by week 4 (the planned value), but you have only completed 40% (the actual value), the variance is 10%. This negative variance tells you the project is behind schedule. Variance analysis also covers cost. If you budgeted £5,000 by week 4 but actually spent £6,000, you have a cost variance of £1,000. The project is over budget.

Another important concept is performance measurement. This goes beyond just identifying variances. It involves using metrics to evaluate the health of the project. The most common method for this is Earned Value Management (EVM). EVM uses three key data points:

From these three values, you can calculate performance indexes. For example, the Schedule Performance Index (SPI) is EV divided by PV. If SPI is less than 1, the project is behind schedule. The Cost Performance Index (CPI) is EV divided by AC. If CPI is less than 1, the project is over budget. These indexes give you a standardised way to predict future performance.

Why does this matter? Without monitoring and controlling, a project manager would only know if a project was in trouble when it was too late to fix it. This process replaces guesswork with data. It forces the project manager to look at objective measurements rather than hoping everything is fine. It also provides a structured way to communicate status to stakeholders, showing them exact numbers rather than vague statements like 'It seems okay.'

Monitoring and controlling also involves change control. When a variance is found, the project manager must decide what to do. This could involve implementing corrective actions (fixing the immediate problem), preventive actions (avoiding future problems), or defect repairs (fixing a flawed deliverable). Any changes to the project plan, scope, or budget must go through a formal change control process to be evaluated and approved before implementation. This prevents scope creep (uncontrolled changes that add work without adjusting the plan).

Finally, this process produces important outputs. The primary output is work performance reports. These are regular updates that summarise the status of the project, including variances, performance indexes, and forecasts. Another output is change requests. When a variance is significant enough, a formal request to alter the plan is created. These outputs are shared with stakeholders to keep everyone informed and aligned.

Imagine you are a project manager at a mid-sized retail company. Your project is to upgrade the company's customer relationship management (CRM) software. The project is expected to take 6 months and cost £100,000. You have a project plan with tasks, deadlines, and a budget. Now, you need to monitor and control this work day-to-day.

Step one: You set up regular status meetings. Every Monday morning, you meet with your development team. They report on what they completed last week and what they plan to do this week. You compare their reported completion against your project schedule. For example, the plan says that by the end of week 3, the database migration task should be 100% complete. The team tells you it is only 80% done. You have identified a schedule variance.

Step two: You quantify that variance. The planned value for the database migration task is £10,000 (the budgeted cost). The earned value is £8,000 (80% of £10,000). The actual cost the team has already spent is £9,000. You now have numbers: a schedule variance (SPI = 0.8) and a cost variance (CPI = 0.89). Both are below 1.0, meaning the project is both behind schedule and over budget on this task. This is a real financial and time risk.

Step three: You analyse the root cause. You talk to the lead developer. They explain that an unexpected data format issue slowed down the migration. They had to write extra code to convert the data. This was not anticipated in the original plan. You now have a clear reason for the variance.

Step four: You decide on a corrective action. You have a few options:

You choose to add a temporary developer. This will increase the task cost by £2,000 but should bring the task back on schedule by week 4. You document this decision and submit it as a change request to the project sponsor for approval.

Step five: You update the project plan. The budget line for the database migration task is increased. The schedule for the next task (integrating the CRM with the email system) is adjusted to start one day later to account for the new developer's ramp-up time. You communicate this to the entire team and stakeholders in your next weekly status report, showing the old plan and the new plan.

Throughout the remaining 5 months, you repeat this process weekly. By continuously monitoring the actual work against the plan, you catch another potential issue in month 4 (a vendor is late delivering the API keys) and adjust again. By the end of the project, you deliver the CRM upgrade only 2 weeks late and £3,000 over budget. Without monitoring and controlling, the project might have been 3 months late and £20,000 over budget, or worse, failed entirely.