I’ve written twice before (here and here) about the severe problems with the British government’s Universal Credit project. From my first post: The British government has spent roughly half a billion pounds ($750M) developing a new IT system for its welfare services, with the goal of cutting down on fraud and loss. The project, by all accounts, has […]
Joseph Marks over at Government Executive Magazine has an excellent article on the propensity of government IT projects to having significant cost/schedule overruns or to fail altogether. One of the key issues is the frequent lack of authority, power, and accountability precisely because of all the rules, regulations, and procedures in place for acquiring IT […]
Over at Kotaku, a Gawker Media web portal that covers computer games (a bigger industry than Hollywood, I might point out), Jason Schreier has an excellent article outlining the fall of LucasArts, once one of the most productive and successful video game companies around, but now no longer in existence. It is worth a careful […]
I wrote last week about problems with the UK Government’s Universal Credit project, an attempt to do a system-wide replacement and re-engineering of IT systems for the Department for Work and Pension. The latest news article now states that the project has already written off £34 million and may end up writing off up to […]
It seems that each year brings another story about a failed or very troubled IT project attempting to replace or re-engineer the computer systems for some state’s Department of Motor Vehicles. The latest is this well-researched and well-written article by Bruce Landis at the Providence Journal about the problems the state of Rhode Island has […]
Classic patterns in disputed IT project: Hertz v. Accenture
Just ran across this article at the always-irreverent-but-usually-spot-on Register, an IT news site out of England. The standard patterns of a troubled IT project are so evident in this one report that I may well use it as a case study for my CS 428 (“Real-world software engineering”) class this fall. Here are some of […]
Neverending Story pattern: School District ERP system late, over-budget
A story a few days ago caught my eye, not because it was unusual, but because it follows so familiar a pattern. Here are a few excerpts from the article: MANATEE — Late nights, hefty contracts and humming computers are a norm in the district’s School Support Center, where employees are working to fix a […]
Minnesota DMV software project: Faulty Towers/Neverending Story patterns
In my 2000 white paper, “Patterns in IT Litigation: System Failure (1976-2000)” [PDF], which I researched and wrote while at PricewaterhouseCoopers, I describe six broad fact patterns to classify the types of software system implementation failure. One of those patterns I named “Faulty Towers”: The client buys the system from [or has the system developed […]
![The Meltdown/Spectre CPU bugs: a dramatic global case of the “Unintended Consequences” pattern [UPDATED 4/4/18]](http://bfwa.com/wp-content/uploads/2018/01/intel-cpu-150x150.jpg "The Meltdown/Spectre CPU bugs: a dramatic global case of the “Unintended Consequences” pattern [UPDATED 4/4/18]")
Back in 2000, PricewaterhouseCooper published my research white paper, “Patterns in IT Litigation: Systems Failure (1976-2000)” (PDF). This paper reflected research I and my staff had done over several months on roughly 120 two- or three-party lawsuits involving information technology. I found that almost all of these lawsuits fell into one or two of six […]