Documentos de Académico
Documentos de Profesional
Documentos de Cultura
LABC21 Template Sites utilise a standard configuration to deliver a set of core functionality. Changes or enhancements to this LABC21 Template requires solid business justification and are approved if this benefits all template sites. The existing change management process was designed prior to the deployment of the LABC21 Template and assumes single-site consultation and approval. Enhancements are needed to the change management process to facilitate the process of consultation with, and approval from all sites for a change request. LABC21 Consolidation project is currently consolidating at least three legacy sites per server. The server hardware itself will be managed centrally in Stevenage by EIS team. Application side of service support remains to be shared within site and also service support team. This operating model is very new to the team and is not having appropriate process in place that will mainly cover changes and approvals related to the servers and also application. The process of managing these changes is seen as very crucial to sustain smooth service, especially since it now involves the integration of multiple teams, including business team.
Owner/Date: Nik Aida Azlina Nik Mustafa 12-Mar-12 5. Proposed Actions or Countermeasures - What do you propose and why?
6. Plan
Central Chameleon Change Raised (Development and Testing ) FBA Form is communicated to Site for awareness of the work involved Site ensures that the Site Change Control details their responsible areas(LSOPs, UAT etc)
The FBA form is completed by the LABC21 Support Analyst who will be managing the RFC
FBA Form is communicated to Site for awareness of the work involved Site ensures that the Site Change Control details their responsible areas(LSOPs, UAT etc)
LABC21 Analyst completes the Estimate of Effort table and inserts into the FBA Form Resource Section
Site Representative added as an additional Business Approver in Chameleon or Wet approval of FBA Form
Site Representative added as an additional Business Approver in Chameleon or Wet approval of FBA Form
FBA is submitted, logged into RFC Log and submitted Central Change Authority
Central Testing
Central Testing
Is the estimated
Central work with site to complete FBA for Loading into Chameleon
amount of effort 10
days or less ?
No
Inform Site Testing is completed and ready for Implementation to Site Test Env
Site sends details to Central Support
Central Error
Site Error
Impact Assessments
Change Implemented
Yes
UAT Successfull
No
Site Raises IR
Approve
Site Error
Continue to next stage of Promotion to Production
Yes
Site Remediation
Site Remediation
3. Analysis Why does the problem or need exist 1. Too many assumptions of the process 2. Process sequence is incorrect 3. Change process is adopted from a single site approval 4. The process of getting the Business Approval is taking a lot of time to get to the implementation stage.
4. Goals and Target - What specific outcome is required 1. Firm up the process to reflect the actual process 2. Cater change process so that it covers the approval invloving multiple sites requirement 3. Reduce the cycle time of getting the Business Approval up to Implementation stage.
Please note that if the Goal or Target Condition is already specified then steps 3 and 4 may be reversed
Title : Owner: Ver: Nik Aida Azlina Nik Mustafa Date: Mentor: PROPOSED ACTIONS or COUNTERMEASURES - What do you proposed and why?
Proposed countermeasure(s) to address each candidate root cause. [This should be a series of quick experiments to validate causal model analysis.] Predicted results for each countermeasure. Assessment Questions 1. Are there clear countermeasures steps identified? 2. Do the countermeasures link to the root cause of the problem? 3. Are the countermeasures focused on the right areas? 4. Who is responsible for doing what, by when (is 5Why-1How clear) 5. Will these action items prevent recurrence of the problem? 6. Is the implementation order clear and reasonable? 7. How will the effects of the countermeasures be verified?
Task Define Problem Statement Understand current condition Analysis Re-design new process Agree acheivable improvements Preparation of Pilot Changes Pilot improvements Implement improvements Improvements Go Live Follow up
Start Date 24/Jan/12 27/Feb/12 16/Mar/12 02/Apr/12 24/Apr/12 23/Apr/12 10/May/12 28/May/12 13/Jun/12 27/Aug/12
Finish Date 31/Jan/12 30/Mar/12 9/Apr/12 23/Apr/12 24/Apr/12 09/May/12 24/May/12 12/Jun/12 13/Jun/12 31/Aug/12