Incorrect paths specified

liz · Newbie Joined: Feb 22, 2008 Posts: 3

Hi all!

I have come across a recurring issue where changes are not implemented as scheduled because one workgroup specified an incorrect path that the implementing workgroup needed to use. Sad

Have any of you experienced this, and what preventative plans did you put in place in the change planning stage?

m_croon · Posted: Fri Feb 22, 2008 7:51 pm Post subject:

TEST!

UKVIKING · Posted: Fri Feb 22, 2008 8:19 pm Post subject:

M_Croon said in a terse style

I will be verbose

The change needs to be tested before implementation

This needs to be enforced
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

liz · Newbie Joined: Feb 22, 2008 Posts: 3

Hi m_croon and ukviking - thorough testing was done, the problem is not with that but with the fact that in the change implementaion instructions a file was specified for copying from a path that was incorrect and the 'correct' path did not even contain a file with the specified filename.

This has happened before, with different groups and individuals.

Ed · Posted: Fri Feb 22, 2008 9:42 pm Post subject:

Hi liz

Who signed off the implementation instructions as being correct?

This is the person you need to target. Sloppy sign-off will always be an issue until you make it less appealing than doing the job properly.

Talk to your Release Manager - this is just the kind of thing he/she should be catching.

Regards

Ed

m_croon · Posted: Fri Feb 22, 2008 9:54 pm Post subject:

liz · Newbie Joined: Feb 22, 2008 Posts: 3

Thanks for the replies .. much appreciated. I have some ideas now that I will explore with the technical guys.

Timo · Posted: Sat Feb 23, 2008 3:16 am Post subject:

asrilrm · Posted: Sat Feb 23, 2008 10:12 am Post subject:

It could be possible that when testing was done, the test environment had a different settings from the production environment.
So it might be possible that the testing went fine but didn't work on production. If this is the case the question is were the infrastructure guys involved in the test, or at least consulted with.
Quite humble but who knows?

m_croon · Posted: Sun Feb 24, 2008 12:19 am Post subject:

Hi,

Still, this has to do with proper testing. Are production and test environments the same. if not, talk to config. and release mgt! They should provide the circumstances for proper testing.

Skinnera · Senior Itiler Joined: May 07, 2005 Posts: 121 Location: UK

With all the talk of testing, I'm not sure that anyone has specifically teased out the importance of post-implementation (as opposed to pre-implementation) testing...?

I'm assuming here that the Change went in and caused an issue, rather than it being rolled back without impact other than wasted time & effort - but I could be wrong. The latter is poor also of course...

You need to collate the data, analyse it, and expose/highlight/sanction those responsible for the failure.

asrilrm · Posted: Tue Feb 26, 2008 1:48 pm Post subject:

You made a point. Yeah, I wonder what happened with the PIR especially since liz said it was recurring Confused

m_croon · Posted: Tue Feb 26, 2008 4:11 pm Post subject:

Hi All,

My guess would be that the PIR (be it explicitly or implicitly executed) is exactly the reason why Liz is here. Smile

Liz,

Is my assumption correct?

Cheers,

Michiel


Create an account	Home · Topics · Downloads · Your Account · Submit News · Top 10


Logos/trademarks property of respective owner. Comments property of poster. Rest © 2004 Itil Community for Service Management & Foundation Certification. SV Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.