The migration plans were meant to finally separate TSB from the IT systems owned by its former parent Lloyds Banking Group. “While the TSB board asked a number of pertinent questions regarding the defender plan, there were certain additional, commonsense challenges that the TSB board did not put to the executive (including why it was reasonable to expect that TSB would be ‘migration ready’ only four months later than originally planned, when certain work streams were as much as seven months behind schedule).” However, the report notes that the board failed to ask key questions after facing months of delays to the rollout, which resulted in the creation of a new migration programme plan dubbed the “defender plan.” “The report explains that this made it impossible for the TSB board to anticipate the serious problems experienced by many customers who could not access their accounts.” “If these findings are right, Sabis rolled the dice by running tests on only one of TSB’s two new data centres and this decision was kept from me and the rest of the TSB board,” Pester said. TSB’s former chief executive Paul Pester, who was ousted months after the debacle, criticised the report’s “scattergun” approach, but said its findings showed TSB’s Spanish parent company Sabadell had “cut corners” with critical IT testing.
0 kommentar(er)
