Gartner Survey Shows Why Projects Fail

Analyst : Lars Mieritz

Published: 1 June 2012 ID:G00231952

A recent Gartner user survey shows that, while large IT projects are more likely to fail than small projects, around half of all project failures, irrespective of project size, were put down to functionality issues and substantial delays.

Key Findings

  • Runaway budget costs are behind one-quarter of project failures for projects with budgets greater than $350,000.
  • Small is beautiful — or at least small projects are easier to manage and execute. The failure rate of large IT projects with budgets exceeding $1 million was found to be almost 50% higher than for projects with budgets below $350,000.

Recommendations

  • To optimize success, look for ways to limit the size, complexity and duration of individual projects, and ensure funding has been committed.
  • Stay on top of costs, especially for the largest projects. Ensure that there are the appropriate mechanisms in place to identify budget variances and/or overruns early. Regularly review how cost estimation is done to understand how accurate and effective your approaches are, and pursue improvement opportunities.
  • Keep the schedule realistic. Many large projects fail because business conditions keep changing after the project scope has been set, leaving a significant disconnect between the agreed-on scope and budget versus what the business will require and pay for by the time the project is delivered.
  • Invest in truly capturing and understanding the business expectations and functionality sought from the project, and ensure that there is initial, adequate allocated funding, as well as good processes in place for revisiting the expectations and required funding at multiple points during the project.
  • Increase the frequency of project status and review meetings, as well as ongoing confirmation of the project’s alignment with business strategy — with an eye toward identifying and cancelling projects at the earliest possible stage that no longer meet company needs. 

Survey Objective

The survey was conducted to provide insights into IT project performance in organizations across North America, France, Germany and the United Kingdom.

Data Insights

Survey data is a useful tool for heads of project management offices (PMOs) to gain a broad perspective on the major causes of IT project failures and to assist in the challenge of identifying, building, and developing the skills and staff required for highly effective project and program leadership.

This research explores the survey results with regard to causes of project failure across three project sizes and provides a tangible reminder for all project and portfolio management (PPM) professionals not to lose sight of the trade-offs sometimes required for delivering projects on time, on budget and with the agreed functionality.1 For the purposes of this survey, small, midsize and large projects were defined as follows (see Figure 1):

  • A small project was one with a budget of less than $350,000.
  • A midsize project was one with a budget of $350,000 to $1 million.
  • A large project was one with a budget that exceeded $1 million.

Figure 1. Distribution of Success and Failure Across Project Sizes

 Source: Gartner (June 2012)

Figure 1 illustrates the distribution of success and failure across project size. The respondents were asked to indicate the percentage of their organization’s IT projects over the past two years that were deemed a success or failure by the business.

In analyzing the collective responses of some 150 participants in the 2011 Gartner five-country survey, the failure rate of IT projects with budgets exceeding $1 million was found to be almost 50% higher than for projects with budgets below $350,000.2 At 25% and 28% respectively, the failure rates of midsize and large projects are similar, and in both cases, nearly one-third higher than the 20% failure rate observed for small projects (with budgets below $350,000). Overall, the results of this survey are consistent with what we have observed when we have polled this question previously, and we are seeing a pattern emerging where small IT projects experience a one-third lower failure rate than large projects 3

Many small brooks make a great river. The survey results give a clear indication that, by ensuring that projects are kept small, and as a rule of thumb, not exceeding six months in duration, a much lower failure rate can be achieved. As such, setting clear criteria around limiting project size will be a hallmark for successful PMOs, and the guiding principle revolves around establishing projects whose scopes and functionality can indeed be delivered in the time frame and, thus, maintaining a clear focus of the endpoint.

Rather than taking on large, expensive and lengthy projects, it will be more prudent to view them as programs consisting of a series of small projects, each delivering its piece of the overall initiative. This will also enable the use of regular program oversight reviews to ensure that the big picture is maintained and to rapidly reassess and recalibrate should any of the individual efforts get off track.3

No matter what the reason, no one likes failures, so in seeking to understand the causes behind the project failures, Gartner asked the respondents to distribute the projects that were deemed to have failed in their organizations over the past two years across six frequently mentioned reasons or causes of project failure:

  • Functionality issues
  • Substantially late
  • Quality issues
  • High cost variance
  • Canceled after launch
  • Rejected or not implemented for other reasons

Figure 2 explores the project failures shown in Figure 1, and illustrates the percentage of failures that respondents allocated to these six typical causes of IT application project failure (see Note 1 for project failure definitions).

Figure 2. Why Projects Fail

 Source: Gartner (June 2012)

It is not entirely surprising to see that the challenges of bringing projects in on time, on budget and with the agreed functionality are mentioned by two-thirds of the respondents as causes of project failure, because this is largely in line with previous observations.4 However, that fact underlines the ongoing nature of these three challenges in the sense that, no matter where you stop and take a snapshot, these three are likely to appear. The key is not to be complacent (we are not the only ones with projects running over), and take steps to understand the particular circumstances in the enterprises so that the right mix of processes, people, tools and skills can be developed or put in place.

Figure 2 also highlights the improvement opportunities that can be achieved simply from improved communications, in the sense that nearly half the projects fial for not doing what they need to do (functionality) or doing it too late to be valuable (late). This hints at project planners not asking the right questions, such as “When is late too late?” or “What scope would you give up to have something delivered sooner?” or reassessing functionality needs with enough regularity that no gap is allowed to develop. Project planners need to be aware of and address changes in the environment, and understand that cost, scope and schedule are not weighted equally. By maintaining close ties to sponsors and stakeholders, and being upfront regarding the trade-offs between functionality scope and schedule, expectations can be recalibrated on an ongoing basis, thus improving success rates.

For organizations at the lower levels of PPM maturity, any effort toward improving scheduling, cost estimation and functionality will yield significant results. For organizations at the higher levels of maturity, we recommend broadening the suite of performance metrics that are used to provide deeper insight into the factors that might be driving the rather persistent greater than 20% failure rate we’ve seen over the years.

Methodology

Gartner conducted a research study in October 2011 to examine current performance of IT projects in North America (the U.S. and Canada), France, Germany and the United Kingdom (see Figure 3).

Figure 3. Geographic Distribution of Respondents

 Source: Gartner (June 2012)

In all, 154 organizations with at least one PMO or related office were qualified and interviewed via a Web-based survey. All respondents were required to manage or work within their organization’s project management function. The resulting sample consists of organizations across various industry segments (see Figure 4) with $500 million or more (see Figure 5) in annual revenue.

Figure 4. Distribution of Respondents by Industry

Source: Gartner (June 2012)

These findings and recommendations from the Gartner survey are in line with conventional wisdom.  

So what can we do differently to help ensure project success?  

The people side of any change programme must be addressed in order to secure success.  

In addition, provide regular feedback to the customer, for example by adopting Agile SCRUM principles of iterative development or implementing new Systems of Engagement practices.  

One fresh area to be considered is Cloud based Development and Deployment.

Introducing Enterprise Cloud Development:

the next evolution in managing modern software development across the enterprise.

Three Industry Innovations have emerged  – Agile Software Development + DevOps + Hybrid Cloud Development & Deployment

Five Step Blueprint for Embracing Enterprise Cloud Development Blueprint

About these ads

22 Comments

Filed under Business

22 responses to “Gartner Survey Shows Why Projects Fail

  1. Pingback: Do You Have a Governance Framework for Successful Project Execution?

  2. Pingback: Communication: the root of all success and failure - John Mackay - For the fans ...you both know who you are.

  3. Thank you for the summary. I really appreciated the acknowledge that some approaches would be better for low vs high maturity organizations. And great brainstorming on what are emerging approaches e.g., Cloud, to accelerate project success.
    Rosemary Hossenlopp
    Knowledge Lead; Organizational Project Management (OPM) Community of Practice http://opm.vc.pmi.org/

  4. Pingback: Data Driven Design with Agile for Data Warehousing | Dimodelo Solutions Community

  5. Pingback: Missão: Resgate - Parte I | Blog da Concrete

  6. Pingback: The Sky Is Blue, Salesmen Lie and Projects Fail | ......dot LEADER

    • Dot Leader blog post – in any org project failure is inevitable. The key is to understand the risk and, return for any given project .

  7. Pingback: The Sky Is Blue, Salesmen Lie and Projects Fail | My Site/Blog | Just another WordPress site

  8. Pingback: 3 Visible Pillars – Cost, Quality, Schedule | bridge360blog

  9. If you’d like to go deeper on this topic, check out Why Projects Fail. It’s a 113 pages book featuring project management case studies, analyze of failed projects, suggestions and recommendations.

  10. Pingback: Healthcare.gov: An avoidable failure by the numbersbitstrategist :: thoughts about 1s and 0s

  11. Pingback: The most common causes of project management failure – Part II | Project Management – A Beginner's Review

  12. Pingback: What Tips Can You Discover in a Failed IT Project? | Information Technology for Manufacturing

  13. Crystal

    Thank you for the statistics. However, I’d like to clarify the meaning of “substantially late” For large IT projects, 28% were substantially late. Does this mean that the projects were dropped/ not used? (since it is included in the failed projects)

  14. Enterprise management of risks, issues, opportunities, dependencies and assumptions is critical regardless of where the landscape is today and where it will be tomorrow. Large or small, spend too little time focused on these and you are much more likely to fail.

  15. Did you use any research paper for reference of this article? If you did then please do refer to them as well.
    The Gartner Study is the reference source. Thanks for your feedback Syed

  16. Pingback: Advice for Junior PMs – #3 – The value of a kick off meeting for a small team | Unnatural Leadership

  17. Pingback: Best Practices in Requirements Management | A Software Architect's blog

  18. Excellent article and thank you for sharing

  19. Excellent article – I found this stat interesting
    6. 60% of failed projects have a duration of less than one year

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s