Since no under April, IBM remains searching inside the issues all around the shocking TSB software rollout that creates a good deal banking discomfort for patrons.
Big Blue knows the main issues appear to derive from insufficient testing and control surrounding software changes. Overall it appears as though the second world war Room’s would choose a problem that was then altered without checking along with other War rooms. This sort of practice features a inclination to compound errors due to inadequate understanding over the impact of change.
Combined with over confident rollout on mass as opposed to numerous stages of testing and roll to rectify issues. It appears shocking with this particular author that any software organisation considering the variety of customers and mainly inside the finance sector will not know to roll when you will see failing, as well as the simple mindedness of TSB really believing they tested everything before putting the unit “live” for the world to discover (crashed and burned).
The IBM presentation document makes interesting studying with several hints for software houses on IBM’s own practices. All the stages they mention and highlight as TSB failures coupled with recommendations might help anybody write an extensive playbook for testing and departing new software.
This ex-software test engineer is please to discover IBM mentioning plenty of errors which can be learnt from by others. I appear to can remember the MD from the organization I did so formerly use stating “We do not require a test department, it is precisely what clients are for”. As shocking as that’s to anybody within the sector it appears that TSB’s test team have forgotten some simple training and could return to enter board.
Eventually you must understand that apparent communication relating to the Software Team, test Team and Management are important, within the situation of TSB I will need to guess in the communications breakdown.
For TSB customers, the nightmare remains very real, for TSB it’s brought to more bad banking press and that has to generate trust issues. Lets keep in mind that publishing faulty code that produces systems to grind having a halt isn’t great, but consider the risk of vulnerabilities within the system and without warning I am glad I do not bank with TSB!