By Tony Collins
On BBC R4’s “Week in Westminster” on Saturday morning (14/12/13) guest presenter Isabel Hardman of The Spectator spoke to Conservative MP Richard Bacon and me about big government projects that go wrong.
Hardman mentioned that Bacon has co-written a book on government failures Conundrum: Why every government gets things wrong and what we can do about it.
Referring to write-offs so far of about £40m on Universal Credit, Hardman asked me whether it was normal for such a write-off on a big project.
I said it wasn’t. The work and pensions secretary Iain Duncan Smith has said it was. When questioned by MPs of the work and pensions committee on 9 December, IDS implied that it was not unusual to write-off a third on large software-based projects. He suggested that research by Forrester supported this view.
Software coding for Universal Credit has cost about £120m so far (excluding hardware, infrastructure, consultancy or other IT-related costs). So IDS suggested that a write off of £40m was only about a third of the software coding costs.
But I haven’t seen any evidence that suggests write-offs of a third of the software costs on a big project are typical.
I replied to Hardman that although there has been much trial and error on Universal Credit IT, £40m is a lot to write off.
[Trial and error included an attempt, from 2011 onwards, to adopt an agile approach but the National Audit Office said the DWP “experienced problems incorporating the agile approach into existing contracts, governance and assurance structures”. The NAO added that the Cabinet Office “did not consider that the Department (DWP) had at any point prior to the reset [Feb-May 2013] appropriately adopted an agile approach to managing the Universal Credit programme”. The DWP has now introduced what it calls Agile 2.0, a hybrid approach incorporating elements of agile with waterfall, though agile purists say it is impossible to combine the two.]
I told Hardman that the write-offs were largely because the DWP was unclear at the outset what the software was supposed to do.”With big IT projects it’s a bit like designing a bridge and you know where one side begins but you’re not sure where the other side ends. They have been learning as they go along and that’s probably why there have been large write-offs,” I said.
Hardman asked Richard Bacon whether it was normal to set out on these big projects without knowing where the bridge was going. Bacon agreed, citing the NPfIT which had led to large write-offs on failed work for England-wide electronic patient records. He said it was not at all abnormal for ministers to set off on big projects without knowing where they were going.
The good news?
I told Hardman that IDS was at least well informed. He now has the NAO scrutinising the project as well as his own external consultants and the independently-minded Howard Shiplee as head of the project.
But I didn’t think UC would be complete until 2020 at the earliest given that the last big computerisation of benefit systems, Operational Strategy, took about 10 years to complete. Hardman said: “That would be a humiliation for IDS surely?”
I replied that IDS may not even be in politics in 2017. I also said that UC will probably not bring the financial benefits predicted, to judge from the last big computerisation of benefits. But UC has wide support. Perhaps, I said, it has to work … eventually.
If a £40M is normal then it damn well ought not to be!
“Software coding for Universal Credit has cost about £120m so far”!!!!
I and many other SME’s could have delivered much more for way less than, finger in the air, 5% of that figure and that includes ramping up with the appropriate staff to do it. These figures are ludicrous and there is simply no way to justify it other than greed and the knowledge that those commissioning this project have no idea about what they want, are doing or how to go about getting it. Who in their right mind starts to build a bridge without knowing where it is supposed to end?
A project of this scale will not work with Agile (there I said it) but by the same token nether will it do so via Waterfall, Spiral or any other methodology for that matter as in such cases Methodology does not maketh man or an appropriate software solution.
I am very angry, especially about the nonsense being espoused: Agile 2.0, really?
Pick up any book on Agile and it will describe the ins and outs of the methodology especially those aspects which deal with team communications. When your development team is small <20 it works very well from a communication perspective. Make that team larger and dispersed and communication becomes far more problematic. Add into that the complexity of the actual requirement and IMO Agile wont cut it. That does not mean that Waterfall will either!
Projects of this scale need to have a very clear goal (the other end of the bridge) and stated set of aims which in essence encapsulate the steps which need to be taken. You don't just jump in there on a politically led whim and think you’re going to work it out as you go along. Correction – you do if you want to spend £120M so far and then write off £40M along the way.
Reality check
Average full time senior developer at 50K – 120,000,000 / 50,000 = 2,400 development man years.
Say project has been running for 3 years (can’t remember when it actually started and when the first line of code was tapped out but you get the picture). 2400 / 3 = 800. Are we to believe 800 developers were working on this fiasco? No. I am sure that there were many contractors riding on this gravy train but presented as permanent staff. Let’s assume only 100 developers and ignore what they are being paid. Let’s focus on how any such project with that number of coders is going function and turn out fit for purpose code on a regular basis, anyone who has designed, built and delivered successful code at the enterprise level will know this bird aint gonna fly.
LikeLike
Pingback: Is £40m write-off on a big software project normal? | Campaign4Change | kickingthecat