Where Control Fits in a Project

Plans are predictions

Every project plan is a prediction made with incomplete information. Some of that prediction will be wrong. Monitoring and control exist to find out where it is wrong, early enough to do something useful about it. The aim is not to make the project match the plan at any cost. The aim is to keep the project heading towards its objectives, using the plan as the reference point for decisions.

This course assumes you already know the basics of planning: scope, a work breakdown structure, a schedule, a budget and a risk register. It focuses on what happens after the plan is approved — when real work produces real data and people must decide what that data means.

Why timing matters more than precision

A problem found early has many possible responses: re-sequence work, use float, bring a resource forward, simplify a design, talk to a supplier before the delay becomes contractual. The same problem found late usually has one response left: accept the delay and the extra cost. The value of control therefore comes mostly from early detection. A rough signal received in week four is worth more than a precise analysis delivered in week twenty.

This has a practical consequence. When you design control for a project, ask first, "How quickly will we know?" and only then, "How accurately will we know?" Many organisations do the opposite and build monthly reports with careful detail that arrive too late to change anything.

What control is not

• Not reporting for its own sake. A report that does not lead to a decision, or confirm that none is needed, adds cost without control.
• Not blame. If variance leads to punishment, people hide variance, and control stops working.
• Not rigid adherence. Sometimes the right control decision is to change the plan through proper change control, because the original plan no longer serves the objective.

Control also has a cost: time spent measuring, reporting and meeting. Intermediate practitioners must judge how much control a project needs. A three-week internal project and a three-year plant construction need very different control systems, though the same cycle sits underneath both.