Joined: Mar 04, 2008 Posts: 1891 Location: Helensburgh
Posted: Fri Oct 12, 2012 10:27 pm Post subject:
Before I answer this question, may I enquire why you do not wish
I suppose it entirely depends on what you wish to encompass in the scope of your release management.
You could take the view that the operational documentation should exist before submission to release management (or even before submission to change management) because it is (or should be) part and parcel of the product.
Or you could design a system whereby it was incorporated into the release process. But I do not see how you can have attained operational acceptance to go ahead before the documentation has been presented to and validated by the operations section. So it surely needs to be in place before the implementation. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Joined: May 17, 2010 Posts: 4 Location: Cardiff, UK
Posted: Fri Nov 02, 2012 11:47 pm Post subject: Re: Before deploy do Release Mgmnt describe new feature to O
What ITIL says? And your real life experience says?
My real life experience suggests that in the work environment people do not like surprises.
In most cases, I'd be looking for ways to give anyone who is affected by the change a heads up on when it's going to happen and what the changes are, and the risks, impact etc. Whether this is something you should be doing or someone else depends on your release process.
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