Which Government Has the Worst IT?

Both the U.S. and U.K. seem to be staking claim to the title

2 min read
Which Government Has the Worst IT?

A few days ago, President Obama was overheard complaining on an open microphone at a fundraiser that US Federal government IT was "horrible ... across the board."  President Obama was soon backed up in his sentiment by Vivek Kundra, the Federal CIO, who was also quoted by Politico as saying, "Federal IT is horrible."

Many Risk Factor blog readers would undoubtedly agree with the sentiment, given just some of the US government IT projects I have posted about over the past several years that have been botched, bungled and or butchered (for a small sample set, see here, here, and here).

However, about six weeks ago, this ComputerWeeklystory reported that Professor Helen Margetts, from the Oxford Internet Institute, told a Public Administration Select Committee looking into "Good Governance: The Effective Use of IT," that her studies show "the UK to be an outlier both in egovernment performance and in the number and scale of IT disasters" in comparison to countries such as Australia, Canada, Japan, the Netherlands, New Zealand and even the United States.

The ComputerWeekly article described the situation in the UK as being "uniquely bad."

Professor Margetts may have a point as well (see here, here and here, for example).

That led me to wondering about who really has the worst government IT: the US or the UK?

Having worked in both US and UK government IT sectors, it really is a difficult choice. 

To try to settle the matter, we have set up a purely unscientific straw poll to determine the winner of "the worst government IT."

Feel free to support your vote or to provide a write-in vote using the comments section. Some Risk Factor blog readers from Australia may want equal consideration for the award, given Myki, the Queensland Health fiasco, and the LINK project.

By the way, in the UK, "government IT" usually covers IT used in civil and local government as well as defence. Therefore, to have a level playing field, when voting, consider that "US government IT" includes Federal, state and local governments. They have their own tales (see here and here) of disaster as well.









 

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}