Before deploy do Release Mgmnt describe new feature to OPS ?

[bluecat]

Gentlemen,

Before deploy any new changes, do you think Release Mgmnt need to describe all those new feature/functionality to Operation Support staff? And then go for deployment.

Or should be after deployed once Release Mgmnt would found new feature/functionality working correctly.

What ITIL says? And your real life experience says?

Thanks.

[Diarmid]

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

[SteveGriff]