I’m involved in the development of a Masters level course on Change Management for e-Business initiatives.
Has anyone been involved in projects where specific frameworks and/or process tools were used to facilitate change? any help would be appreciated.
I’m familiar with a few lifecycle models which some corporations use… I’ve used a couple in my own projects - but am interested in hearing from people who have more experience in this area.
I have this book: Foundation in IT Service Management (itSMF). Its a summary of Service Support and Service Delivery, where as the change management process is described throughly the service support book publisher OGC/TSO, I think thats the blue book.
I have some very nice power point presentation, would have sent it to you, but its in german, so of no use for you.
Let me know if this is enough information for you.
I don’t know much about change management (the rules, codes etc) but for a while i had to attend some change management phone conferences where there would be a boss of some sorts who would be presiding the meeting while a number of other people would present their cases. Whatever department that change affected to would have to okay that change (atleast one person from the client side and one from the IT solutions provider side) and then finally the big boss would green light the change.
To me though it was an hour of putting myself on mute and listening to guys yell and cuss each other out for an hour
The client i'm working for at the moment is very big on change management. I'm not aware of what lifecycle they are following but I can take you through the sequence of processes they follow.
They have a change management system where cases are logged... Then, a person would raise a change request in the system if a change indeed is required to close the case. After raising the change request, an RFC (Request for change? i think) form is filled. The copy is sent to the process owners from the technical and business side for approvals. When the RFC form is approved, the approval evidence is attached to the RFC Form and the Form is attached to the Change request in the system with statuses set to pending approval. Ths is then picked up b the change manager for a CAB(Change Advisory Board) meeting held every Monday and Thursday. The case is dicussed and you are then given an official go ahead to start work on the change.
After the change is implemented, it has to be tested in the QA environment, getting user acceptance testing from the business... and evidence is attached to the RFC form and status of the Change request updated on the system.
Once it has been successfully tested and the evidence of testing is recorded and the statuses and RFC forms updated, this is again picked up by the change advisory board (CAB) meeting held on Thursday. It is discussed and you are given Authorization to move it into the Production environment/system. The changes have to be tested in Production now, and the statuses updated accordingly and the case is closed.
Phew! Took me ages to write that down,,, imagine how long and annoying it can be sometimes even for tiny little changes.
Dont know if that is of any help to you but thought I'd share the process followed by one of the biggest confectionary companies in the world atleast in their Asia Pacific wing anyway.
What KAKA mentioned also in pratice the change request (RFC) has to be documented in the CMDB(Configuration Management Database) CMDB holds information about all CIs (configuration items) in the company, changes that are approved have to added in the CMDB by configuration Management.
Change Management makes sure that standard methods of changes are implemented and misktakes and incidents are prevented.
FSC is the schedule of chance ( Forward schedule of change ) also known as the Event Database.
CAB/EC = Emergency committee. (for urgent changes/ major problems)
PIR = (Post Implementation Review) is a Rewiew after the change has been implentated.
I'm going to be adopting heavily from the ITIL guidelines. Are there specific resources that you can recommend.
Six sigma will be more of a quality focused approach wheareas I'm interested in a project centric approach.
Project centric approach could be nasty in functional organizations... nobody likes to give up their sweet spot easily, especially if the organization is structured that way. Different models of change management faire better in different environments.
What school is this course being designed for. Is it for an eMBA?
umar so far the definitions used seem to be very I/T focused. is that your intent or are you looking at the broader picture because the impact is on systems, processes, and people..individually and teams/depts.
I feel thatthe i/T aspect is just on part of the change mgmt, an important part but just one part.
are you familiar with the PLOT frameowrk of Bain (Plan Lead Operate Track)