Information Management PADM 7110 Arnold Watson Change Management in IT

Change Management Practitioner’s Definition The Change Practitioner’s definition of Change Management is the orchestration of change in a way that identifies and addresses the human risks involved in implementing change. This strengthens the individual and organizational ability to handle change well and increases the chances that the change will be put successfully into practice. Source:

IT Change Management Definition IT Change Management is the process of requesting, analyzing, approving, developing, implementing, and reviewing a planned or unplanned change within the IT infrastructure. The Change Management Process begins with the creation of a Change Request within the company’s selected technology platform. It ends with the satisfactory implementation of the change and the communication of the result of that change to all interested parties. Source:

Principles of Change Management

Address the “Human Side” systematically Start at the top Involve every layer Make the formal case Create ownership Source:

Principles of Change Management cont. Communicate the message Assess the cultural landscape Address culture explicitly Prepare for the unexpected Speak to the individual Source :

IT Change Management Process

Formally Request a Change Categorize and Prioritize the Change Analyze and Justify the Change Source :

IT Change Management Process cont. Approve and Schedule the Change Plan and Complete the Implementation of the Change Post-Implementation Review Source :

IT Change Management Workflow Task

Initiating the Change Identify the Need for Change Provide Information to Identify Requirements Source :

IT Change Management Workflow Task Analysis and Initial Approval Phase Create a Request for Change (RFC) Assign the Change Category Assign the Change Priority Source :

IT Change Management Workflow Task Development Phase Developing the Business Case Justification Technical Impact Analysis Business Risk and Impact Analysis Approvals Required for Change Based on Risk Level Risk Level Based Lead Times Source :

IT Change Management Workflow Task Development Phase Continued Lead Time Guidelines Developing the Backout Plan IT Business Unit Manager Review and Approval Testing Conducting the Peer Approval Source :

IT Change Management Workflow Task Change Approval Phase Emergency Priority Changes are Escalated to Appropriate IT Business Unit Manager Routine Changes are Approved by Appropriate IT Business Unit Manager and Progressed Directly to the Change Implementation Phase Minor Changes can be Approved by the Change Coordinator or Appropriate IT Business Unit Manager Source :

IT Change Management Workflow Task Implementation and Documentation Phase Final Planning Scheduling and Notifications Change Implementation Testing, Validation, and Acceptance Source :

IT Change Management Workflow Task Change Review and Acceptance Monitor Change in Production Environment Hold Post-Implementation Review Accept Issue and Continue Source :

IT Change Management Workflow Task Measure Quality in the Change Change Reports Change Compliance Source :

Conclusion Approximately 80% of IT service outage issues are a result of systems updates and alterations. Therefore, utilizing a well developed IT Change Management plan is one way of taking some of the risk out of IT change projects. Source: based_it_change_management.pdfhttp:// based_it_change_management.pdf

References Fickenscher, Kevin and Michael Bakerman “ChangeManagement in Health Care IT.” Jones, John, DeAguirre, and Matthew Calderone “10 Principles of Change Management.” Strategy-business.com.