Chowrangi

Proper use of a change management system relies rather heavily on a configuration management tool and it get replenished by having a proper Extraction, Transformation and Loading process.

I am actually, despite some poor experiences, rather in favour of automating call and change management - much better on relying on someone who has been around for years and knows everything, and actually probably more efficient, especially if it avoids the story about how we should never have had that system in the first place and do you remember the days of netware 3.1 and…. What I find incredibly frustrating is that I have never seen IT departments apply critical thinking to their own implementations, we seem to be some good at reining in bad project plans, except when they are our own.

People tend to use call and change management systems because they know that they aren’t following that discipline already, but if they buy a system they’ll somehow have to. Still can’t use technology to automate behaviour, just a lesson from the eighties that’s not been learned yet.

There is a very glaring problem with chain management systems, feed them wrong info and rest assured it will get propagated very rapidly and widely: good old GIGO. Same goes for configuration management: who can guarantee what’s there is correct, other than verification and auditing?

Other posts by Commoner

• Israeli Massacre Goes On - January 7th, 2009
• Gilani's Fight - January 7th, 2009
• Unfortunate Remarks - January 6th, 2009
• Collective Urgency - January 6th, 2009
• Dismal Performance, Huge Rewards - January 5th, 2009
• Blood in Gaza - January 4th, 2009
• Troops Movement Should be Halted - January 3rd, 2009
• Reconciliation Joke - January 3rd, 2009
• Bent on War - January 3rd, 2009
• Attack on the Victim - January 2nd, 2009