Change management is a wonderful world. You take an IT Production that is already running with patches, temporary fixes, recurring incidents and IT Heroes committed round the clock to preserve the fragile balance between order and chaos and, instead of doing necessary long term investments in time, money and people to cleanup and stabilize what painfully exists, you decide to change something, there, now, at 4:55pm, five minutes before the night batch starts running 1500 jobs on 500 servers…
Of course, the test procedures are, more than often, resolved through the “GANEMITBO paradigm”: Go Ahead, Never Mind the Bollocks!
Tested or not, the change must go ahead, because it is a “business issue”. More than often, the change is just a correction of a bug caused by another change. Not yesterday, but last week…
Anyway, tests are often useless. Not because we don’t have time to. But because test platforms environments do not exactly match those of the production. Nobody never have time to work on test platforms: everybody’s committed to fix the bugs on yesterday’s changes…
Aucun commentaire:
Enregistrer un commentaire