11 replies
by jamesrl
I don't really care what system you use to track - I've used excel spreadsheets.
What we would do is have a weekly meeting, review all the outstanding changes, understand the impact of those changes on each other, on already scheduled activities and try to see where they might fit. Its nto the tracking method, its making the decision - we had the change sponsor, the network gang, the data centre gang etc all in the room to decide wheter it made sense.
We tried to fit changes into a regular maintenance window. We tried to build enough buffer to test the changes during the window and enough time to back out if needed. We also ensured that if there could be a backout plan, everyone knew what it was and how to initiate it.
James
by markross
by rhomp20029
The company I worked for before I retired had 190K employees all over the world. Data processing people everywhere. Trying to get all the signatures was a nightmare. We had telecon meetings to discuss all these changes but due to one of the senior members we ended up rehashing all the minor stuff to the point that it took 2 hours of which the major changes got about 10 minutes if that and we never got the final word because just about that time the senior members would have to go to another meeting just when we needed their input and approvals. We tried to handle it by email but that ended up with the same problem.
Then there was the problem of stuff that was important for Europe or Asia but not the US. That was another one that used up all sorts of time where we were supposed to hang in there listening while all this other stuff was gone over and over so the US senior members could understand it. What we should have done was divide up the meetings so that the US stuff only could be handled by itself, the foreign stuff by itself and the joint stuff by all of us. Could never get the seniors to agree to that. Result was trying to get the clients to go along with us until the signatures could be gotten.
I sometimes wonder how these people ever got their senior jobs. Was it just that everyone else left who was above them? Peter principle in action? Apparently the changes that our clients were screaming for were low on their totem poles.
We do change control here as well, we are required to by Sarbanes-Oxley.
It is a time-consuming, laborious process...but it does have a couple of upsides.
One of them is that CYA (Cover Your A**) should be a part of the system.
We are required to wait for documented IT management approval on all changes. We do this by using the MS Outlook "voting" feature, and attaching the sent message (with its tracking tab, saved as an .MSG file) to the work order.
This not only provides SOX proof of the approval without signatures, it lets whoever is complaining about lack of productivity see when the message was sent and when the manager clicked the "Approve" button.
by markross
Bill,
You provide a good point, and one the I forgot about. Thanks. I also like how you used MS Outlook as a tool in the process. Unfortunately I work in a Notes shop and will have to research if the same feature exists in Notes. I appreciate the input.
by tig2
Recently left one- used a specific change control database that had the decision tree built in for electronic sigs. Especially good if there is a hierarchy that has to be followed. The way that Notes handled the notification it had to be "passed" but each signature received went back to the originator.
Grab your Notes Database Designer and ask him/her what thoughts they have.
Change control can be a good thing. I have seen some nightmare cases where it wasn't followed. Broke a whole lot of remote users for about three months before we were finally able to track down the root of the problem.
Oh- designed correctly, that Notes database can also serve as a dashboard for changes that are waiting on approval.
by rhomp20029
by rhomp20029
by larenm
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending