T5: an acknowledged disaster
BA: software failures key in T5 fiasco
08 May 2008, Tom Young, Computing
http://www.computing.co.uk/ctg/news/1819345/ba-software-failures-key-t5-fiasco
Software failures were a key part of the Terminal 5 fiasco (T5) last month, but it is still unclear whether British Airways (BA) or BAA are responsible, a Commons Transport Committee heard yesterday.
BAA is responsible for the contracts with IT suppliers, and so takes part responsibility for costly baggage system errors in the first three days of T5 opening.
But BA is responsible for training staff to use the systems correctly, including the correct procedures in the event of software failure.
"We compromised on the testing regime and this impacted on operations, but this was because of delays in the completion of the building programme," said BA chief executive Willie Walsh.
However BAA were responsible for the building programme, and thus for rushed testing.
"The totality of the testing regime did not adequately reflect the first few days of operations," said BAA chief executive Colin Matthews. "There were then a number of problems that arose very specifically from within the software."
These software issues were identified relatively quickly, but the knock-on effect on operations became catastrophic, said BAA non-executive chairman Nigel Rudd.
Neither BA or BAA currently plan to sue any suppliers.
Reader comments
© Incisive Media Investments Limited 2012, Published by Incisive Financial Publishing Limited, Haymarket House, 28-29 Haymarket, London SW1Y 4RX, are companies registered in England and Wales with company registration numbers 04252091 & 04252093
Businesses who ignore the importance of testing do so at their peril
It is depressing to hear that the disastrous launch of Terminal 5 was in part due to a lack of software testing. Testing is a fundamental part of software development and implementation. Too often it is marginalised and undervalued - often considered as an expendable part of the project. I sympathise with BA who have had to learn this lesson the hard way.
Testing software quality at every stage of the project lifecycle whether developer, functional or load/performance testing, can be the difference between a successful roll-out or one that is riddled with problems and, in the case of high profile developments, often ridiculed in the media. Rigorous and regular evaluation of progress against objectives ensures that problems are spotted at an early stage, allowing on-going adjustments to correct issues and keep the programme running on time and to budget.
Businesses who ignore the importance of testing do so at their peril. Costly IT systems that do not meet business or customer expectations can not only harm an organisation's productivity and performance, but can also leave an indelible mark on its brand.
Yours sincerely,
Steve Gedney
MD, Borland UK & Northern Europe
Posted by: Steve Gedney - MD, Borland UK & Northern Europe 14 May 2008