Tuesday, December 06, 2005

Why Are Projects Over Budget?

It's a project management epidemic. For years now, the figures have remained pretty much the same. Seventy-five percent project failure rates, many of which come in over budget.

I believe there are three reasons for this.

1) Project managers not tracking the budget closely enough. My view on this is that this is the least frequent reason. Project managers are under siege to monitor costs closely (and it's an indelible part of the process in some organizations), and still the projects don't come in on budget.

2) Bad estimates. Now we're getting closer. Are we learning from mistakes? Do we have checklists to alert us to necessary resources and standard execution times for tasks? If so, much of this can be remedied fairly easily.

3) Pressure to lowball the budget to get the project approved. Ah-ha! This is the silent killer of projects. I contend that project managers frequently either feel compelled to promise a low budget or are pressured to succumb to a low budget in order to get a project approved, and that this is the reason why most projects end up over budget.

In a worst-case scenario, all three reasons exist (and, indeed, this happens more often than we care to admit), but I contend that the third is the most overlooked cause of project failures.

Lesson: Don't feel pressured to come in with a lower budget than you anticipate the project will really need. Stick to your guns when it comes to presenting the case. If the project gets declined, you're better off.

Labels: , , ,

1 Comments:

At 10:27 PM, Blogger Jerry Manas said...

In thinking about this further, there's a fourth reason. Some projects are reported as being overbudget, but they're not.

For instance, if an agreed-upon baseline revision is approved, the metrics should be based on the revised baseline. Some organizations base all their metrics on the original baseline.

While I agree that the original baseline should be preserved, metrics should be based upon agreed baseline revisions, and any discrepencies vs. the original baseline should be reported separately via a post-project review.

However, if a project is simply over budget, then I wouldn't revise the baseline at all. You can request additional funds without setting a new baseline.The project now has the funds authorized, but it's still over budget.

Revising the baseline should typically only be done because of requested scope or schedule changes or approved changes in approach. Or because a new project phase is being planned, and the baseline is being set piecemeal (by phase - in a Rolling Wave environment).

Saving a baseline is one of the most controversial processes in project management, as there doesn't seem to be wide consensus on the rules of revision.

 

Post a Comment

Links to this post:

Create a Link

<< Return to PMThink! Project Management Gateway