In a follow-up interview, the CEO of SWA explained they were implementing a new release of the purchased app that cratered under the load--and that they'd implemented EIGHT releases in the prior year. NINE releases of a large, on-prem, app suite--with custom mods, integrations, and undoubtedly UX/CX/report/database changes in one year??? He wanted to sound reassuring, but nine releases of a complex, critical system in a year should scare the heck out of Board members!
And that FAA database error was also scary. A critical system shouldn't allow an employee to just overlay a production database. Again, it looked like they were saying, "Nothing to worry about; just a dumb contractor." And again, where are the IT checks and balances that ensure components are validated before migration to production?
Great post, John!
In a follow-up interview, the CEO of SWA explained they were implementing a new release of the purchased app that cratered under the load--and that they'd implemented EIGHT releases in the prior year. NINE releases of a large, on-prem, app suite--with custom mods, integrations, and undoubtedly UX/CX/report/database changes in one year??? He wanted to sound reassuring, but nine releases of a complex, critical system in a year should scare the heck out of Board members!
And that FAA database error was also scary. A critical system shouldn't allow an employee to just overlay a production database. Again, it looked like they were saying, "Nothing to worry about; just a dumb contractor." And again, where are the IT checks and balances that ensure components are validated before migration to production?