Joined: Sep 16, 2006 Posts: 3570 Location: London, UK
Posted: Fri May 06, 2016 4:54 pm Post subject:
You need to split hairs
1 - If the change as designed was implemented successfully, then it was a successful change
2 - The degradation to the network service is a fault.
If the analysis of the gfault and the restoration process of whyit degraded points to the change, then this is a architectural question and of course why the change got approved as the risk and impact identified was flawed _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
In my company this would be a scored as a failure (Introduced Bug/Incident). It was proven to have an unanticipated negative impact.
Black and White to me for this example. But I'm fairly strict on things in my company. This is not to prove people are bad (far from it), its for learning purposes. My company often goes back to change records to find out how something was performed, knowing about this incident that was caused might help prevent the same from happening in the future.
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