We do code pushes to production on Thursday nights. We have a rule that all updates must be tested in the test environment, and sent to the sys admins by the start of the 4 PM Wednesday update review meeting, or else it either has to wait until next week, or a separate emergency change ticket has to be created (for true emergencies only). Last week, one of our business analysts came up to me on Thursday morning and said, "Oh, I forgot to mention, we need to do X update for this customer, they're expecting it this week. It's been tested and everything, I just forgot to include it on the list yesterday." I told him it would require an emergency change on Friday instead. That was fine.
This week, 20 minutes before the 4 PM Wednesday meeting begins, he sends me an update that "must go this week", then retracts it 10 minutes later. At this point, I asked his boss to "please address these last minute additions & subtractions" with him, because they are frustrating for the sys admin team to keep track of. I probably should have left it at that, because his boss did respond and said he would take care of it (which I later found out he did, first thing this morning), but today I arrive, and this BA is asking to remove something else that was added to the change ticket the day before.
I responded as tactfully as I could without having any caffeine in my system yet. I summarized it with, "C, this is the third time in the last week you've asked for an 11th hour addition/subtraction. Could you please help us understand why this is happening, and determine what we can do to avoid this as a team going forward?" As soon as I hit send, I realized I was probably going to regret it, having gone a little above my pay grade.
Hour later, drive-by b*tching from his boss. "Would you stop sending out these *ing public blasts singling out members of my team? Etc. etc."
We settled it in short order, but I still think it was worth the p155ing match.
