Gartner research director Darryl Carlton gives a preview of his presentation at the Gartner Application Architecture, Development and Integration Summit, 21-22 July 2014 in Sydney.
Over the last few years, we have seen an increasing number of high profile government IT projects end in spectacular failure.
Take the British Child Support Agency for example, which ranks as one of the worst public administration scandals of all time. Not only did the system have an 85 percent error rate in calculating payments but, seven years after it was introduced, there were so many complex rules involved that the system was completely undeliverable.
In Australia, it took the tragic death of an 11-year-old boy to highlight the massive failure of the Victoria Police LINK crime-reporting project. A report by the Victorian Government Ombudsman described the project as ‘fatally hampered by a poorly constructed business case that grossly underestimated the cost and complexity of the problem’. Worse, it took the project team four years to identify the project was $80 million under-funded.
These two agencies are not alone. The BBC, Sky News, Homeland Security, the US Air Force, and even Queensland Health have all had similar failures.
Why do these projects fail?
1. Business process complexity
It sounds simple, but one of the most important reasons projects fail is that governments bite off more than they can chew. Projects are too big, too complex, too ambitious.
If the public sector is to stem the rate of failure, they must find ways to reduce the complexity of the ICT systems and technologies that underpin it.
2. Portfolio management
For 30 years, IT has been telling businesses there is no such thing as an IT project; that it’s a business project and the business, as a whole, needs to take ownership; that the most important IT person in the enterprise is the CEO.
You know that old saying ‘be careful what you wish for because you just might get it’? Well, business listened and took control. IT leaders are now trying to reign in ‘shadow IT’ that has become so rampant it now represents 36 percent of all public sector IT spend.
Business leaders have taken it upon themselves to make complex IT decisions, often dismissing CIOs as being too technical when they raise concerns.
Having pushed for business ownership of IT decisions, we now have even bigger problems – IT spend is out of control, and IT success is as elusive as ever.
3. Governance and risk management
In most of the failed government projects, governance arrangements were found to be less than effective, and responsibilities were so diffused that it was difficult to identify who was accountable. Senior officers were reluctant to make critical decisions and project steering committees didn’t have the requisite expertise.
By muddying the waters of who is responsible for ICT-enabled projects, we have lost sight of what needs to done.
We must remember that business is not the customer and cannot dictate whatever it wants. The new reality is that business partners with IT to deliver outcomes and value to the real customer of the enterprise.
Learn more on how government CIOs can protect against project failure at the Gartner Application Architecture, Development and Integration Summit, 21-22 July 2014 in Sydney.
Gartner, Inc. (NYSE: IT), is the world's leading research and advisory company and a member of the S&P 500. We equip business leaders with indispensable insights, advice and tools to achieve their mission-critical priorities and build the successful organizations of tomorrow.
Our unmatched combination of expert-led, practitioner-sourced and data-driven research steers clients toward the right decisions on the issues that matter most. We're trusted as an objective resource and critical partner by more than 15,000 organizations in more than 100 countries—across all major functions, in every industry and enterprise size.
To learn more about how we help decision makers fuel the future of business, visit www.gartner.com.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.