by Phillip Smith
Project planning is an exercise in forecasting. The idea is to take the variables you can account for and try to anticipate any issues that might rain on (or dry up) your project’s progress toward a smooth conclusion. Forecasts are rarely perfect, which is why we have project managers still assigned to projects even after the plans are built. We need the PM’s there to lead teams through time and change and keep the project in scope.
That’s why the real mark of a good PM is discernment on the fly. PM’s, while leading their teams, must be able to distinguish the difference between normal variation from plan and real trouble–and be able to recognize the difference between the two in time to mitigate and control. Sometimes re-planning is required, but the goal in most instances should be to return to the original plan whenever possible.
So how do you know the difference between normal variation and real trouble in a project? A textbook answer would involve the use of metrics plans. If defects (severity, volume), schedule variation, budget, or productivity reach beyond established thresholds, then corrective action must be taken. The metrics required to monitor the project are expensive, and we don’t all have them available to us. So many PM’s are working without formal metrics, and must diagnose real trouble before it is too late. Fortunately, there are some general rules of thumb. Ailing projects have some common symptoms, many of which formal metrics account for and an observant PM can easily identify. Here’s what to watch for:
Classic Symptoms of an Ailing Project
High defect rate
Unexpected costs, or lack of expected costs
Low team morale or other HR issues