Discussion Locked

Implement strong change request procedures

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

How does your organization handle change requests? How do you think you could improve the process? Share your comments about establishing effective change request procedures, as discussed in the Aug. 31 Disaster Recovery e-newsletter.

If you haven't subscribed to our free Disaster Recovery e-newsletter, sign up today! Click this link to subscribe automatically:
http://nl.com.com/MiniFormHandler?brand=techrepublic&list_id=e061

1 reply

by stress junkie

I have worked in a couple of places that had implemented a highly bureaucratic change request procedure. This often placed system administrators in a difficult position. There are times that the resolution to a problem is not known in advance. The system administrator has to make a list of several possible problem causes and list a possible resolution to each potential cause. If a system administrator has to make a change request for each possible cause/resolution before he knows the resolution to the problem the change request will be useless and is likely to be denied.

In other words, problem resolution is often too dynamic. Once the resolution is found it is already implemented. Does one make a change request after the change has been made? If so then what is the point of the approval process?

This discussion is closed to new replies.