Posted: Tue Apr 03, 2007 1:34 am Post subject: Is there a "Root Cause" of KEs from development?!
New subscriber and keen Service Management chap here – I would be interested to hear opinion on something please
An organisation I am working with is starting to push on getting Known Error (KE) info from new and upgraded services. These are highlighted through a formal Service Introduction process.
The KEs are getting logged in the Problem Management tool and assigned appropriately, to be investigated for fixing. That aspect is fine, but there is very recently a call to add the same Root Cause categorisation as is recorded for reactive Problems.
I'm uncomfortable with this as it really feels like it is different information. Capturing the RC info for reactive Problems tells us where we have deficiencies to address - Do you think you can actually have a 'root cause' for a KE that has come from Service Introduction? If so there is surely a requirement to highlight it as non-reactive? It just doesn't feel right!
Posted: Tue May 15, 2007 1:05 am Post subject: Release Notes
Understanding your question correctly... Yes you can have RC from Dev. Those are the issues they are still working on or decided not to resolve when going live with the specific change. You definately like to keep track of those in the (logical) KEDB.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum