18 September 2014

How to Prevent Project Failure in 2014

Project failure is expensive, embarrassing and alarmingly common. Depending on your estimates - 5%-30% of all projects are successfully completed. Getting to the bottom of project failure is an important way to improve our project performance. If we don't put in the effort to learn, how will we ever make progress?

Project failure is a problem in every industry and every country. Consider the following statistics.

I know what you’re thinking. The data above come from surveys that are a few years old. Surely the project management field has made advances. Perhaps new project software and procedures have significantly improved results? Unfortunately, project success remains challenging for most organizations in 2014.

“Men make history and not the other way around. In periods where there is no leadership, society stands still. Progress occurs when courageous, skillful leaders seize the opportunity to change things for the better.”  - Harry S. Truman, U.S. President

Recently, I read the PWC report on project management. The PPM 2014 Global Survey draws on the comments from people in 110 countries and more than 3000 respondents – an outstanding global view of project management. Let’s consider the four main failures causes of project failure and what we can do to overcome those problems.

Poor estimates in the planning phase

Estimates remain one of the enduring challenges of project management. That makes sense since projects are about change and creating something new. I can estimate travel time in my home city with reasonable accuracy. The first time I visited Lisbon or London, I found it difficult to estimate travel time because it was unfamiliar.

To improve estimates, the report suggests:
  • Using a multi-step process to validate estimates.
  • Call on the knowledge of subject matter experts (e.g. software developers) to validate estimates

To those ideas, I would also suggest that project managers should make greater use of their internal network. There is a great deal of project experience that has never been committed to writing. It is up to you to discover this knowledge by building relationships.

Change(s) in scope mid-project

In the U.S. Congress, government spending is subject to “pork.” This is the tendency of elected officials to demand additional funds be spent on projects in their areas, even if the projects are of dubious value (e.g. the infamous Gravina Island Bridge “bridge to nowhere” project proposed in Alaska with a +$300 million project).

At this point, you might be thinking, “oh those foolish politicians.” Think again! How many times have executives, sponsors and other stakeholders undermined a project by adding additional requirements. Unless these requests for additional features are carefully managed, the project will soon collapse under the weight of scope changes.

PWC’s recommended solution to managing scope creep include the following ideas:
  • Design project plans with flexibility in mind. Built-in flexibility means a change of attitude on scope.
  • Adopt a portfolio approach to projects to discourage tinkering with project scope

Insufficient resources

Seeking more responses is the battle cry of many project managers. It is a natural tendency in life to seek out more resources when you feel that you are running out. Unfortunately, organizations are limited in how much budget and staff they can assign to projects. Thoughtful project managers need to find other ways to respond to the challenge of insufficient resources. 
  • Ask other project managers how they solved resource shortages
  • Call in favours from your network, from time to time

Bio. Bruce Harpham writes about project management training, leadership, productivity and related topics at Project Management Hacks. His project experience includes leading projects in higher education and financial services.

No comments:

Post a Comment