Urgent changes: WTF?

Excuse me if I’m rude, but many idiotic things have happened around at my office: we’ve finally launched our new service desk tool, after 9 months developing it (average time spent at other clients was 1 or 2 months). Though it was meant to be ITIL compliant and so support the adoption of the framework, our IT manager has decided to, er, redefine some ITIL terms, specially those regarding change management and SLAs.

So, he has introduced a new type of change: urgent changes. Nothing to do with emergency changes: urgent. What’s an urgent change? A change to be done ASAP. But not in an emergency case, ie: a project manager wants to deploy his new version of app X, and he wants it now. This new version doesn’t solve a major issue with the previous release or adds functionality that the business imperatively needs due to legal issues or whatever reason you can think of for an emergency change, because, and that’s the point, it’s not an emergency. Usually, it will just be a project deadline too close and a project manager unwilling to take the blame for the delay of the release (why take the blame when you have the IT crowd to take that blame as “they won’t deploy the app until next week”?).

Where I see nothing but fighting what a best practices framework dictates, my manager and his mates think they’ve had a great idea because with urgent changes they show how customer oriented they are. Bullshit.

And WTF, where the hell have they read on ITIL core books the term “urgent change”???