Upload
balaji-reddy
View
215
Download
0
Embed Size (px)
Citation preview
8/8/2019 Change Process Training Ver 01
1/37
Change Management
Process
8/8/2019 Change Process Training Ver 01
2/37
Agenda
Change Management Process
Roles & responsibilities of individuals involved in change
management
Challenges you may face in Change Management
May 2009 Change Management Training 2
ow o overcome e pro ems an wor owar simprovement of Change adherence
8/8/2019 Change Process Training Ver 01
3/37
Change
8/8/2019 Change Process Training Ver 01
4/37
Change
What is Change?
Any installation or alteration in
Hardware System
Application software
Configuration
May 2009 Change Management Training 4
which adds to, deletes from, or modifies theservice delivery environment or its attached
network is termed as Change.
8/8/2019 Change Process Training Ver 01
5/37
Change
We GMC are responsible for adhering to changemanagement process for: Hardware level changes in Routers / Switches / Firewalls
Software changes in Routers / Switches / Firewalls Changes in LAN
Any changes in applications, directly being managed by us.
May 2009 Change Management Training 5
Objective Implement changes within agreed time frame
Minimize the duration and impact of any service outages
associated with a change Address root cause of change failure
8/8/2019 Change Process Training Ver 01
6/37
Roles
8/8/2019 Change Process Training Ver 01
7/37
Roles
Change Requester
Field Support Team
Change Authorizer
Helpdesk or Service desk Team
Change Controller
Change Approver
May 2009 Change Management Training 7
Change Implementer
8/8/2019 Change Process Training Ver 01
8/37
Responsibilities
8/8/2019 Change Process Training Ver 01
9/37
Change Requester
Any individual either Customer, IBM-GMC or 3rd party vendorsmay initiate a change request, but the same has to be authorizedby authoriser (SPOC) before sending to GMC.
A Change Requester owns a change request from the time arequest is raised to its final closure.
A Change Requester will perform business and technicalassessments in order to set the category / schedule of the change.
May 2009 Change Management Training 9
A Change Requester will raise the change request and will alsoensure that the change request is approved.
A Change Requester will provide required inputs or any additionalinformation to change implementer for planning the change.
A Change Requester will verify & confirm the change success afterit has been implemented by implementer.
8/8/2019 Change Process Training Ver 01
10/37
Field Support Team
Support team will provide inputs to implementer, Authorizerfor implementation plan and impact analysis.
Support team will confirm the equipment readiness and
availability of required capacity at site.
Support team will be available at site during the activity.
Support team will facilitate the change implementation and will
May 2009 Change Management Training 10
e prepare or ac -ou .
Support team will assist in getting the confirmation fromrequester, post change.
Support team will compile location specific change
management data, tracked for monitoring quality of changes.
8/8/2019 Change Process Training Ver 01
11/37
Change Authorizer
Change Authorizer is the person who will authorize the change request initiatedby the change requester.
Change Authorizer will send the RFC to GMC Helpdesk.
Change Authorizer will follow up with customer / approver to ensure timelyapprovals and also will obtain downtime approvals
Change Authorizer will ensure the Expected Implementation Date / Timeadheres to Green Window (00 hrs to 06 hrs everyday for Major & Mediumchanges) & expected TAT.
May 2009 Change Management Training 11
Change Authorizer will coordinate with CRB members for approval foremergency changes.
Feedback & monitoring Change Authorizer will confirm the success of change implementation to
GMC.
Change Authorizer will ensure a tracker for monitoring quality of changerequests is maintained. They will ensure correctness of data & share with PMon fortnightly basis.
8/8/2019 Change Process Training Ver 01
12/37
Helpdesk
Helpdesk will register the RFC in Service desk
Helpdesk will send the notification of the ticket details to the requestorin 30 mins as per communication plan
Helpdesk will assign the change ticket to respective group in absenceof Change controller.
Helpdesk will publish SMS for scheduled Medium & Major changes.
May 2009 Change Management Training 12
Helpdesk will follow the ticket till closure & will make sure that ticketnotes are up-to-date.
Helpdesk will report the discrepancy, if any
8/8/2019 Change Process Training Ver 01
13/37
Change Controller
Change Controller is the owner of the overall change process and has the final authority toaccept / reject the change
Change Controller is the primary interface into the change process and representscustomers interests and IBM needs to meet service commitments.
Change Controller owns the responsibility for the adequacy & accuracy of accepting ®istering a RFC and handling notifications / communications, executed by Help Desk.
Change Controller will monitor the change request for impact analysis, correct criticalityand validate that the change request has been assigned to the correct ChangeImplementer's.
May 2009 Change Management Training 13
Change Controller will identify and resolve schedule conflicts, also decides if the changerequest requires assessment and further approval from other stake holders.
Change Controller will provide a final go-ahead to change implementers for executing thechange.
Change Controller will coordinate and participate in the Change Review Meeting and trackthe process health.
Change Controller will lead the CRB and present all the planned changes. Facilitate theparticipation of right people in the change process
8/8/2019 Change Process Training Ver 01
14/37
Change Approver
Change Approver will evaluate/assess the risk or impact level of thechange on IT production environment, which is provided by the ChangeRequester.
Change Approver will decide whether the change can be implementedas scheduled or need to be deferred/ cancelled. i.e. gives formalapproval / rejection of the change.
Change Approvers role will be played by the Customer, who in turn will
May 2009 Change Management Training 14
.
Change Approver will give the technical go-ahead for Medium & Minorcategory changes, for the implementation plan from GMC L3/L2.
Change Approver will participate in the CRB for Major categorychanges of their respective location.
8/8/2019 Change Process Training Ver 01
15/37
Change Implementer
The Change Implementer identifies and provides the technical skill and resources toplan, control, and execute the change on a day-to-day basis.
Change implementer will prepare implementation plan (L3 for Major, Medium andpreauthorized Changes and L2 for Minor changes) and email to stakeholders as percommunication plan.
Change implementer will execute the change as per plan and update the ticket statuspost execution (L2).
Change implementer will send the closure email, notifying affected parties whether thechange was successful or unsuccessful and get confirmation from requestor afterimplementation (L2).
May 2009 Change Management Training 15
Change implementer will update the configuration database if any configurationinformation changes.
While executing a change, if the implementation overruns the approved downtime: Back out Perform the required activities & reschedule the change Cannot be backed out and additional downtime required log as an incident, take
approval for additional downtime from change requester, authorizer & approver andcomplete the change
Cannot be backed out and no downtime required complete the change and record theadditional time taken while closing the change ticket
8/8/2019 Change Process Training Ver 01
16/37
Process Steps
8/8/2019 Change Process Training Ver 01
17/37
Change Process Flow
May 2009 Change Management Training 17
8/8/2019 Change Process Training Ver 01
18/37
Major Changes
May 2009 Change Management Training 18
8/8/2019 Change Process Training Ver 01
19/37
Major Changes
Template to be used
Expected TAT Time taken to prepare implementation plan after receivingauthorized request ownership with Netsol (GMC) 2 working
daysTime taken to obtain approval on implementation plan &downtime approval ownership with Customer
Time taken to execute the change after receiving approvals onChange Plan ownership with Netsol (GMC) 4 working days
RFC Template
May 2009 Change Management Training 19
an s approve n , act v ty w n ow w t ownt me
approval is finalized during CRB discussion)
ImplementationPlan prepared by
GMC L3
Final ApprovingAuthority
CRB held on every Friday
Remarks
8/8/2019 Change Process Training Ver 01
20/37
Medium & Minor Changes
May 2009 Change Management Training 20
8/8/2019 Change Process Training Ver 01
21/37
Medium & Minor Changes
Template to be used
Expected TAT Time taken to prepare implementation plan after receivingauthorized request ownership with Netsol (GMC) 12 working
hrs for medium changes & 8 hrs for minor changesTime taken to obtain approval on implementation plan &downtime approval ownership with Customer
Time taken to execute the change after receiving approvals onChange Plan ownership with Netsol (GMC) 12 working hrs
RFC Template
May 2009 Change Management Training 21
or me um c anges rs or m nor c anges
ImplementationPlan prepared by
Medium Changes GMC L3
Minor Changes GMC L2
Final ApprovingAuthority
Bharti Location SPOCs
Remarks
8/8/2019 Change Process Training Ver 01
22/37
Emergency Changes
May 2009 Change Management Training 22
8/8/2019 Change Process Training Ver 01
23/37
Emergency Changes
Template to be used
Expected TAT NA
ImplementationPlan prepared by
Team assembled by Change Manager
Final ApprovingAuthority
CRB emergency meeting convened over conference call
RFC Template
May 2009 Change Management Training 23
Remarks Only changes required to resolve incidents will be treated asemergency changes.
Nokia/Ericsson Location SPOCs to send RFC followed up by aphone call to GMC.
After change implementation plan is prepared, Location SPOCswill arrange a conference call with CRB members & obtainapproval.
Change Manger to ensure that all required documentation iscompleted within 24 hrs of change implementation.
8/8/2019 Change Process Training Ver 01
24/37
Preauthorized Changes
GMC L3
Start1. Prepare ChangePlan (Sheet 1 of Pre
Authorized RFC)
CRB 4. ApproveChange Plan?
Change
Manager
2. Share Plan withChange Manager
3. Present ChangePlan in CRB
15. Follow CRBRecommendations
5. Share Plan withNokia/Ericsson &IBM Site SPOCs
No Yes
May 2009 Change Management Training 24
GMC
Implementer
GMC Helpdesk
End
Nokia/Ericsson
Location SPOCs
6. Obtain RequiredDowntime Approvals
7. Fill Sheet 2 of PreAuthorized RFC
9. Send to GMCHelpdesk
10. Register RFC &Notify Location
SPOC
11. Assign to WorkQueue
12. ImplementChange & Update
Ticket13. Send Updates
14. ConfirmChange Success
8/8/2019 Change Process Training Ver 01
25/37
Preauthorized Changes
Template to be used
Expected TAT Time taken to execute the change after receiving (downtime)approvals on Change Plan ownership with Netsol (GMC)
Major preauthorized 2 working daysMinor preauthorized 6 hrs
ImplementationPlan re ared b
GMC L3
RFC -Preauthorized
May 2009 Change Management Training 25
Final ApprovingAuthority
CRB
Remarks Change Manager will circulate all approved preauthorizedrequests (1st sheet of attached template) to all Location SPOCs
Location SPOCs to fill the 2nd
sheet of the template (on needbasis) and share with GMC Helpdesk
8/8/2019 Change Process Training Ver 01
26/37
Measurements
May 2009 Change Management Training 26
8/8/2019 Change Process Training Ver 01
27/37
Control Points
May 2009 Change Management Training 27
8/8/2019 Change Process Training Ver 01
28/37
Change Urgency
May 2009 Change Management Training 28
8/8/2019 Change Process Training Ver 01
29/37
Change Category
May 2009 Change Management Training 29
8/8/2019 Change Process Training Ver 01
30/37
TAT
Turn around time
The turn around time is calculated from the time thechange request is submitted, to the scheduledimplementation time.
TAT is used to ensure adequate assessment and
May 2009 Change Management Training 30
.
TAT
8/8/2019 Change Process Training Ver 01
31/37
CRB
In Change Review Board Meeting Review and approve major and preauthorized change
requests.
Review all emergency changes implemented since the lastCRB meeting
Conduct post-implementation review of all major changescarried out since last CRB meeting.
May 2009 Change Management Training 31
Discuss unauthorized changes, if any, since last CRBmeeting.
CRB Meeting is held once a week.
Emergency CRB can be called by the CRB chairperson orCRB member if a change needs to be implemented inBlackout zone or Change Freeze period.
8/8/2019 Change Process Training Ver 01
32/37
Change Window
Change window is used as a tool for approving implementationdate & time for various changes.
Green ZoneAll major & medium planned changes should be implemented only
during the green Zone.00 hrs to 06 hrs everyday.
Blackout Zone
May 2009 Change Management Training 32
.
exceptions need CRB members approval.
Change FreezeChange freeze can be declared during periods, when resourceunavailability is foreseen. Examples of such periods can be festivalperiod etc.
Any change implementation during this period (includingemergency, unscheduled and preauthorized) requires approval ofCRB members.
8/8/2019 Change Process Training Ver 01
33/37
Challenges in Current Change Process
Quite a few changes resulting in unexpected incidents
Changes exceeding the approved downtime
Turnaround time for implementing changes perceived to
be higher than desired Change related communication & related preparedness
not very effective
Partici ation of all ke stakeholders not as re uired
May 2009 Change Management Training 33
No feedback being captured from requesters wrt qualityof implementation / communication
Process for Emergency Change is not followed properly
No role clarity on who is supposed to do what wrt
change management process
8/8/2019 Change Process Training Ver 01
34/37
How Do We Improve Adherence
Understand the roles & responsibilities of our self & ofdifferent teams wrt Change Management Location SPOCs Field Support
IBM GMC Team Central SPOCs of Bharti, Nokia/Ericsson, IBM
Review and strengthen change management process for
May 2009 Change Management Training 34
Monitor adherence to revised change managementprocess and its controls
Build-in continuous feedback mechanism from change
requesters
Team to be aware & confident of Change Process
8/8/2019 Change Process Training Ver 01
35/37
Abbreviation & Definition
SD : Service Desk
HD : Help Desk
RFC : Request For Change PCR : Policy Change Request
PM : Project Manager
May 2009 Change Management Training 35
TAT : Turn Around Time CRB : Change Review Board
8/8/2019 Change Process Training Ver 01
36/37
Feedback Time..
Training FeedbackForm
Please fill the attached sheet and send [email protected]
8/8/2019 Change Process Training Ver 01
37/37
Thank You!!