Most IT Projects Fail. Will Yours?

This content is syndicated from by Kelly Waters. To view the original post in full, click here.

Most IT Projects Fail. Will Yours?Studies on project failure are easy to find and make depressing reading.

Gartner studies suggest that 75% of all US IT projects are considered to be failures by those responsible for initiating them.

But what do they mean by failure?

They mean the solutions fundamentally did not do what was agreed. Or they missed deadlines. And/or came in over budget. Indeed half of the projects exceeded budget by 200%!

A Standish Group study, again in the US IT industry, found that 31% of projects were cancelled outright and that the performance of 53% of the all projects was so worrying that they were challenged.

Some questions that need to be answered in assessing whether a project is fundamentally a success or failure?

  • Has the project satisfied the business requirements of the primary stakeholders?

  • Were the deliverables produced on time and within budget (or as amended by agreed change control)?

  • Do the business owners *perceive* the project to be successful?

  • Has the project delivered the business value promised in the original case for doing it?

I’ve scanned the Internet and read all sorts of articles and research on project failure, and consolidated them into a long list of reasons why IT projects most commonly fail. I've managed to eliminate all the duplicate reasons and boil it all down to these common areas, although it's still quite a long list, unfortunately for IT and project managers!

Project Initiation & Planning Issues

  • Unclear or unconvincing business case

  • Insufficient or non-existent approval process

  • Poor definition of project scope and objectives

  • Insufficient time or money given to project

  • Lack of business ownership and accountability

  • Insufficient and/or over-optimistic planning

  • Poor estimating

  • Long or unrealistic timescales; forcing project end dates despite best estimates

  • Lack of thoroughness and diligence in the project startup phases

Technical & Requirements Issues

  • Lack of user involvement (resulting in expectation issues)

  • Product owner unclear or consistently not available

  • Scope creep; lack of adequate change control

  • Poor or no requirements definition; incomplete or changing requirements

  • Wrong or inappropriate technology choices

  • Unfamiliar or changing technologies; lack of required technical skills

  • Integration problems during implementation

  • Poor or insufficient testing before go-live

  • Lack of QA for key deliverables

  • Long and unpredictable bug fixing phase at end of project

Stakeholder Management & Team Issues

  • Insufficient attention to stakeholders and their needs; failure to manage expectations

  • Lack of senior management/executive support; project sponsors not 100% committed to the objectives; lack understanding of the project and not actively involved

  • Inadequate visibility of project status

  • Denial adopted in preference to hard truths

  • People not dedicated to project; trying to balance too many different priorities

  • Project team members lack experience and do not have the required skills

  • Team lacks authority or decision making ability

  • Poor collaboration, communication and teamwork

Project Management Issues

  • No project management best practices

  • Weak ongoing management; inadequately trained or inexperienced project managers

  • Inadequate tracking and reporting; not reviewing progress regularly or diligently enough

  • Ineffective time and cost management

  • Lack of leadership and/or communication skills

I'm sure we've all seen projects with all or some of these issues. You know, those projects *other people* run :-)

In reality, probably ALL projects have many of these issues. But somewhere there is a threshold. An undefined point where the issues are material to a project's chance of success, or its likelihood to fail. If only we knew where that point was!

A few things struck me when compiling this list:

Not one article or piece of research I read (and I read quite a few!) mentioned risk management. Not one. Lack of proactive risk management. Inability to identify or mitigate risks. Lack of focus on risks. Not one article or piece of research that I found. So that got me thinking. If we don't seem to acknowledge risk management, and we certainly don't seem to see it as a cause of failure, are we to believe that we as an IT industry have got risk management cracked? And if so, why do so many of our projects fail?

Secondly I was thinking about how agile principles help to mitigate these risks? I have a strong view that agile methods help with some of these areas a lot, although I'm not sure all. And it also got me thinking that I don't recall reading about any formal mechanism or process for risk management within agile methods - unless I've missed or forgotten it. There's quite a bit of risk management inherently built into agile principles and practices, but there doesn't seem to be any explicit risk management discipline.

Thirdly, I started thinking about risk management in more formal project management methodologies such as PRINCE2. Risk management is certainly a key discipline there. But one of the key things I was taught as a PRINCE2-based Project Manager (once upon a time I was one), was to only highlight risks unique to the project, because there's no need to highlight the *usual* risks. We all know software development projects might run late, for instance. So we don't need to articulate it on a formal project proposal, or in the risk log, etc. But if we don't articulate and mitigate the *usual* risks, aren't we ignoring the risks most likely to cause our project to fail?


See also:
Reduce your risk of failure
How agile principles help with these issues
DIY Guide for Fixing a Failing Project - by Mike Cohn
10 Key Principles of Agile Software Development
10 Good Reasons to do Agile Software Development

Leave a Reply

Your email address will not be published. Required fields are marked *

12 − one =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch