1). A temporary infrastructure problem pops up at all hours of the day or week and takes the entire application out. At best kicking the users to the logon screen, worse case, ugly dirty error screen with a full load of stack information. Question is what damage has been done to the data? Who knows? Who cares? What if it happens again? Can infrastructure provide a guaranteed fix?
2). More serious a defect(s) in the application which means a code fix. These are the ones that can be reproduced and they don't go away no matter how hard you try until the code has been fixed. Fixed, now it's time to jump through the loops of unit/integration testing(if your lucky), system testing, UAT testing and Preproduction smoke testing.
Do we have to do a data conversion or fix? Whats the impact? How long will it take?
Finally the out of hours deployment and smoke testing before allowing the users back on to the application.
Does Application Support have documentation to support the change(s)?
To be fair no matter how well an application has been developed, edge cases will present themselves and sometimes at the most inappropriate times. Good luck with that!
No comments:
Post a Comment