Project Jupiter Lawsuit Orbits Closer

UK Court Rejects Appeal by Accenture in Dispute with British Gas

1 min read
Project Jupiter Lawsuit Orbits Closer

While the Texas-IBM IT outsourcing saga has been slow-marching towards what seems an eventual court fight since 2008, another high-profile on-going IT project contract dispute has been playing out in the UK courts over that same period.

According to ComputerWeekly, the UK Court of Appeal has rejected an appeal by Accenture to dismiss the claims of British Gas against it in relation to the ill-fated Project Jupiter customer-billing system.

As I blogged about here (and here and here), British Gas is suing Accenture for £182 million over an IT system project it claims reduced British Gas's customer-billing process to a "shambles."

British Gas claims the billing project "was the cause of the appalling customer service that lost British Gas hundreds of thousands of customers," a High Court writ from Centrica [the parent company of British Gas] says.

In addition, British Gas claims that it had to employ 2,500 extra staff to help resolve the billing problems Accenture created.

British Gas believes that it is now on very firm legal ground in its case against Accenture. Accenture, of course believes otherwise.

The trial is scheduled to begin on 3 October 2011.

I am still betting on a confidential, out-of-court settlement.

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
A plate of spaghetti made from code
Shira Inbar

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