Re: Er ...
I believe the correct terms are "agile" and "scrum".
232 posts • joined 1 Jun 2012
Indeed, a controlled, phased migration of customers should have been the strategy here with copious amounts of usage and stress testing and a bullet-proof rollback strategy just in case. I would have thought it would be fairly straightforward to identify the senior director who gave the green light...
On the contrary, customers should get very agitated. This is a core banking platform migration, so there should have been extensive contingency planning, testing and a fallback system in place.
"to help identify and resolve performance issues in the platform"
A good rule of thumb is to do this BEFORE going live.
"Now you have it, we'll now lock you in because that would be cheaper than you buying all new stuff"
To a certain extent, yes. But, as there is a hardware component almost always involved somewhere, when said component needs to be replaced, then it's goodbye and goodnight (probably for ever).
One way would be application functionality, i.e., your application has some whizzy things that your competitors do not, but you're always taking the risk that the customer will migrate anyway because of the cost, or security concerns, or the support experience, or any number of other factors.
Biting the hand that feeds IT © 1998–2021