Change mgmt is about Change processes in example,
you wants upgrade Java, MQ, deploy a lot of applications so in right path you have to create change process.
There are a lot of people like, Change manager who is approving parts,schedule times, actions, then Change designer who design whole process who will do which action and should know technical process needs
(wls team upgrade->unix team-> reboot->monitoring team start monitors after reboot->WLS team start environment,etc..) then teams in this Change ticket receive action tickets (each specialist dedicated in his time) and Change ticket is assigned to Change builder who controls each actions and coordinates teams.
Change ticket has to have planned test process and backup/rollback process too. Then if all actions are completed, builder can close Change ticket and it is send to manager for revision that all was ok and report it to Customer service manager or directly to customers contact.
Changes are usually used when you do big actions which take more time or is more critical change to environment or is needed production maintenance or need shutdown production for some time, etc. Should be planned 14 days before action. Usually actions are planned to out of office hours.
you wants upgrade Java, MQ, deploy a lot of applications so in right path you have to create change process.
There are a lot of people like, Change manager who is approving parts,schedule times, actions, then Change designer who design whole process who will do which action and should know technical process needs
(wls team upgrade->unix team-> reboot->monitoring team start monitors after reboot->WLS team start environment,etc..) then teams in this Change ticket receive action tickets (each specialist dedicated in his time) and Change ticket is assigned to Change builder who controls each actions and coordinates teams.
Change ticket has to have planned test process and backup/rollback process too. Then if all actions are completed, builder can close Change ticket and it is send to manager for revision that all was ok and report it to Customer service manager or directly to customers contact.
Changes are usually used when you do big actions which take more time or is more critical change to environment or is needed production maintenance or need shutdown production for some time, etc. Should be planned 14 days before action. Usually actions are planned to out of office hours.
No comments:
Post a Comment