I run a CAB weekly, as a Change Manager, and as part of any new change requests we require the Change Initiator to complete a Business Case to be attached to the request. This does not have to been a full blown Business Case as for a Project but it still has to cover all the relevant areas such as:
Impact - IT Infrastructure CI's from people to computers.
Reasons for Change
If any change request comes to the Change Manager without this information I simply return the request pending an update that includes the above information. Of course, for this, you need Management buy-in or people will simply try to walk over you and force the Change throug.
I would suggest to include your Problem , Capacity and Availability management teams in the loop of assessing the impact of the change (even the Financial management body, if you have one) so the CAB has really an accurate assesment of the impact of the change to base their decision on. _________________ JP Gilles
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