Why Do Many IT Projects Fail?

Many organizations have experienced projects that failed to deliver on time, on budget, or the scope that was initially intended.  Statistics show that more than 40% of IT projects fail to meet one of the three dimensions above.  One of the key factors organization leaders have to recognize that every strategic initiatives they start must be managed as projects or programs.  Mark A. Langley, President of Project Management Institute (2012) mentioned that all strategic change in an organization occurs through projects and programs.  Organizations have two types of work: operational work where they respectively have to perform a certain activity with a systematized process, the other type of work is where the work has a definite start and end that can be classified as projects.

These projects must follow a lifecycle and have constraints that many organizations fail to acknowledge resulting in project failures.  Below are five main reasons why projects fail and how these areas can be controlled.

  1. Executive Support or Clear Sponsorship:Often projects are initiated and after project work starts executives or sponsors are not engaged.  They leave Project Managers alone and do not get involved until there are surprises.   How to Mitigate: One of the most important factors in project management is planning.  Keeping the executive sponsors involved/informed must be a part of the project-planning phase.  This is project manager’s responsibility, to ensure executive sponsors are informed throughout the project.  I have experienced when executives are too busy and do not want to be involved.  In these situations, I recommend project managers to make sponsor’s acknowledgement and approval of project deliverables as critical milestone.
  2. Lack of Communication:I will start with a quote from George Bernard Shaw, “The single biggest problem in communication is the illusion that it has taken place.”  There have been many occasions I hear project managers complaining, “but I communicated that…”, this happens when we assume that our communications/emails were read and no response means people have no questions.How to Mitigate: You must plan for communication.  Many project managers fail to plan for communication thinking communication is a given task.  If we do not plan, we are certain to miss some communications.  Make sure you have action items and remind people to complete these action items.  A project manager must spend most of his time communicating.  A good project manager spends 90% of his/her time communicating.
  3. Imprecise Business Objective:It may seem difficult to believe that organizations will have projects without proper business objective.  However, in the real world there are many organizations that have a portfolio much bigger than they can manage or fulfill.  They take on these initiatives without proper analysis of workload causing an unhappy work environment.  Cynthia K. West, Ph.D., Vice President of Project Insight mentioned, “Executives play a key role in this issue.  Some organizations have not adequately defined their goals and strategies.  If top management is not clear on project priorities, then it follows that the entire organization is also unclear about which projects are the most important.”How to Mitigate: During your project charter and requirement gathering, it is essential that project managers control the project scope.  Many project managers do not push back to executives in order to avoid conflicts or in fear of losing their job. It is important for project managers to build good scope definitions, project plans, and efforts required to deliver the expected business objectives.  This will help them educate executives on what and when their expectations can be delivered.
  4. Skilled resource availability:Generally, management moves internal resources from one project to the other without aligning their qualifications for the project needs.  Also, at times lower qualified resources are selected to save cost.  Another issue transpires when resources’ workload is not taken into consideration and more and more projects are added to their portfolio.  This results into poor performance and dissatisfaction with the job.  How to Mitigate: Primarily, it is important to have a resource plan completed within a project management plan.  This document must include resource effort required, resource qualifications, and backfill required for internal resources that are pulled into projects.  Project managers should also be able to mentor less experienced resources.  Joseph Gulla (2012) emphasized, “Actively recruit skilled personnel through internal and external routes like jobs systems.  A good outcome will not result without sufficiently skilled people.”
  5. End User Involvement:I have seen many projects where functional managers are making decisions on operational functionalities of the new or upgraded system.  Many times this results in system failure as end users are not able to adopt the system changes.  How to Mitigate: End users are very important stakeholders as they will be using the system day in and day out.  Where functional managers are looking to build all their requirements, the system must be user friendly. If the end users do not adopt the system, no matter how good your system is, it will not be successful.  It is important to identify these stakeholders upfront in the planning phase and that they are involved in major milestone reviews or conference room pilots

Conclusion: 

The key reasons some organizations have poor project success are that they are forced to manage their projects with tight deadlines and cutting budgets to achieve their intended results.  It is essential that we invest in strong, effective project management within an organization in order to increase project performance.  You must have noticed that for each of the mitigations I emphasized on planning.  As Alan Lakein said, “Failing to plan is planning to fail.”  Project Managers must spend a good amount of their time in project planning and make sure they follow their Project Management Plan.

References:

Gulla J., (2012) “Seven Reasons IT Projects Fail, Avoiding these pitfalls will help ensure success” Retrieved from: http://www.ibmsystemsmag.com/power/Systems-Management/Workload-Management/project_pitfalls/?page=3

Langley M. A., (2013) “PMI’s Pulse of the Profession™ The High Cost of Low Performance.” Retrieved from: https://www.pmi.org/~/media/PDF/Business-Solutions/PMI-Pulse%20Report-2013Mar4.ashx

West C. K., (unknown) “Four Common Reasons Why Projects Fail” Retrieved from: http://www.projectinsight.net/white-papers/four-common-reasons-why-projects-fail

Leave a Reply

*

Be sure to include your first and last name.

If you don't have one, no problem! Just leave this blank.