Monday, 21 September 2009 00:00

How Many Things Can Go Wrong...

Rate this item
(0 votes)

It is common that when I am called into fix a red project to have management assign all of the projects ills to one problem. As of yet, I have to see such a project. There are multitudes of problems deeply embedded in the organization and the project team to make a project truly crimson. Managers look at how the problems manifest themselves, skip diagnoses and assign blame. Prior to getting to the point of calling an outside party, they have tried to fix the issues by attacking these symptoms. This only makes matters worse and the project becomes a deeper shade of red.

A red project never has one problem causing its ills. Following is a representative of many projects. This list of issues cited in one small project:
  • Scope creep
  • Maintenance included in the project
  • End user undefined
  • Project Sponsor undefined
  • Executive Management not monitoring the project
  • Product maintenance group missing
  • Authority not delegated to people that needed it
  • Trying to do too much with the skill set involved
  • No decision making
Three items were determined as root causes:
Figure 1 - Symptoms Versus Root Cause

The key to bringing a project back from red is the ability to distinguish the symptoms from the disease. This is very difficult for someone on or associated with the project. The patient are too involved, too attached and too emotional. They need a physician to review the complaints and develop a prognosis and treatment.

It is easy to blame symptoms they are most visible. Scope creep is a common one. However, scope creep is always only a symptom. One or more root causes are the real problem. It may be that the customer fails to understand what they really need. It is possible that Project Manager is allowing change to take place sans management or they are restricting the essential changes. The team could be slipping in new scope to meet the wishes of the customer and avoiding the processes. It may be a combination of any of these. This happens with waterfall and Agile methodologies. Ignoring the process creates havoc. Trying to solve the problem, however, without finding its root cause, will result in more frustration and ultimately failure.

Figure 1 provides an example of an actual project and the list of symptoms that people were claiming to be the root problems. In analysis, they all stemmed from four issues. Initially, scope creep was the base reason. Shortly into the project audit, however, it was obvious that there were two groups claiming to be the end user, each having different requirements. Without defining the end user, the sponsor was unable to prioritize the features. Even with a well-defined scope, the inexperienced team was unable to provide the infrastructure and features in a monolithic delivery—it was simply too complex. Without proper decision making, the authority to phase the project was unavailable and no one could push to remove the maintenance tasks from the project. It all looked like scope creep that is out of control.

As opposed to management's attempts to blame the project team, the problems were primarily outside the project team. Fixing the three problems outside the project and phasing the delivery solved the problems with the project. The corrective actions were put in place and a junior Project Manager completed the project.

Read 7083 times

Related items

  • Process Mapping

    Process is at the core of any business. It makes work predictable, repeatable, and transferable. Without it we cannot scale our businesses. However, process can be a bane to making progress. Processes that work for a $10 million company have difficulties supporting a $30 million company. Trying to scale them to a $300 million company will not only fail but not address the issues that larger companies have that were never dreamt of in a smaller organization. Processes need to be discarded, revamped, and built—all of that without creating an overburdening bureaucracy.

    Anytime you need to go someplace, you first have to know where you are. Processes are never static and your company's current state is probably far from where you think it is. Hence, the first step is mapping out you company's current state followed by defining the future state. This is more than a logical map of the process; it must also include physical maps. Whether your process is solely to provide a service (say, website development) or physical (say, manufacturing) there are logistical issues that complicate the process flow. Without fully understanding those nuances, future state processes will not reach the desired efficiencies.

    For more information about process mapping fill out the form to the left and we will get in touch with you.

  • Success vs Culture

    The other day a Latvian student contacted me for my views the connection between culture and success criteria—an important and intriguing topic. After working in Taiwan, Singapore, Korea, Japan, Israel, United States, and Canada, I wear many scars of both blatant and subtle cultural violations. I also know that within a culture one person's success is often another person's failure. So, after dispelling concerns about clicking on some random email link, I completed her survey (please feel free to take it yourself). In the process, I struck up a friendship with the student, Kristine Briežkalne, who is studying at Riga International School of Economics and Business Administration . She has some interesting views and presented me with a Venn diagram showing four frames to a project (business, client, project management, and growth perspectives) and how they intersected. As the diagram is part of her Master's thesis, I will let you ponder the how to label the overlapping areas (an eye-opening exercise).

  • Kill The White Knight

    There is a reason we do not teach classes on fixing failing projects. Many a cynic feels that we simply do not want to teach our trade, however, our reason is far nobler—we should be teaching prevention rather trying to create white knights to save the day. It is the same philosophy as building a fence at the cliff's edge rather than an emergency room at its base. Our language is replete with idioms telling us to look past the symptom and address problems at their root cause. 'An ounce of prevention versus a pound of cure' or 'a stitch in time saves nine.' Please, feel free to supply your own in the comments. Unfortunately, most of our businesses loathe this philosophy, waiting to address an issue until it is irrefutably broken.

  • The Executive-Project Manager Gap

    It was such an innocuous question, "Working on an article; what is the biggest problem you see with project governance at orgs? Can you comment?" Can I comment? Really? That is like cheese to a mouse. Where could I start—bureaucracy, draconian process, poor executive sponsorship, disengaged leaders? Plenty of fodder, because they all lead to project failure. I fired off, "Creating an over bureaucratic morass stifling innovation & implementing process instead of cultivating leaders." Then the maelstrom started and it went directly to the gap between the executives and projects managers. Naomi Caietti, Robert Kelly and I had a great conversation. Most of the thread is below.

  • Disband Your PMO

    After nearly 30 years of project work, I struggle to understand the role of a project management office (PMO). Even though, I have written of the pros and cons, and read a plethora of articles, opinions, and how-to guides little has been done to convince me that the PMO is reducing project failure. It seems to be nothing more than a tool to fill a void in leadership? Even the acronym, which is so widely thrown around, has little meaning as the "P" has no less than four meanings. It is an executive's crutch for their lack of understanding in how projects work. These, like other, unattended holes in the corporate accountability create opportunities for new and greater bureaucracies and empires that further obfuscate accountability.

Leave a comment

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References

Sitemap