Home Articles Introducing Change Management

Introducing Change Management

PDF Print E-mail

Change Management is an important function in any organization. But, understanding how to implement change management can be very difficult. This article will help you get started by defining some of the essential first things that you need to implement change management. First, let's look at the definition of change management as described in leading industry standards and frameworks.

Understanding the Terminology

The IEEE publishes an authoritative online resource called Sevocab which has the distinct advantage of listing the industry standards where the particular term is used and described. Sevocab describes Change Management as "the judicious use of a means to effect a change, or a proposed change, to a product or service".QuotationSevocab describes Change Management as "the judicious use of a means to effect a change, or a proposed change, to a product or service".Quotation
IT Service Management (ITSM) industry framework ITIL v3 describes change management as the process responsible for controlling the lifecycle of all changes. The primary objective of Change Management is to enable benficial changes to be made with minimum disruption to IT services. (Service Transition, p, 229)

Getting Started

In practices, effective change management requires that you implement an automated workflow to help manage the change management lifecycle. Each change should be introduced by a Change Request (CR) which describes exactly what needs to be done to implement the change. CRs are typically reviewed by a Change Control Board (CCB) which has the authority to authorize or deny a change request. The CCB may not know every technical detail necessary to make the right decision about a change request. To help with this effort the Change Advisory Board (CAB) should assist with advising on the potential downstream impact of a change. Members of the CAB are usually subject matter experts (SMEs) for a particular technology and can advise on the potential downstream impact of a change. The CCB however, is more focused on the process of change management and often has to rely upon the CAB for technical advise.

How Much Process Do We Need?

The automated workflow should consist of a CR initiation, followed by review and approvals often with a meeting of the CCB to discuss and evaluate the change request. But how much process is really necessary. The best approach is to take a lesson from Agile and Lean development and only have the absolute minimum amount of process necessary. If this turns out to be insufficient then you will usually need to add an additional step (usually considered a control) to avoid a mistake. The best source of additional IT controls is often from retrospectives held post release which discuss what went well and what needs to be improve. In a future article, we will discuss how help desk incident and problem management can also provide guidance on additional IT controls needed.

 

 



More articles by this author

Join us at the Agile Development Conference for IT Governance and Compliance in an Agile World Date: Wednesday November 07, 2012 2:15pm Presenter: Bob Aiello, CM Best Practices Consulting Description: Establishing IT governance and compliance practices is essential for organizations that have regulatory or audit requirements. The good news is that you can be agile and still comply with Sarbanes-Oxley, CFR 21, HIPAA, and other regulatory imperatives. Done well, IT controls actually help you improve both productivity and quality. Bob Aiello describes how to implement IT controls in frameworks such as ISACA, Cobit, and ITIL v3 that many regulatory frameworks require—while maintaining agile practices. Bob’s guidance includes specific examples of establishing IT controls: separation of duties, work-item to change-set traceability, physical and functional configuration audits, and more. Bob explains how these practices help government, defense-related, and other critical mission corporations scale agile practices where audit and regulatory compliance is a must. In fact, Bob attests to the fact that a disciplined approach to agile can improve the productivity and quality of most all agile development efforts. Also, please join us the day before for Configuration Management Best Practices training    
Join us at the Better Software Conference for Configuration Management Best Practices training Date: Monday, June 2nd, 2013 8:30 AM Presented by  Bob Aiello, CM Best Practices Consulting Description Robust configuration management (CM) practices are essential for creating continuous builds to support agile’s integration and testing demands, and for rapidly packaging, releasing, and deploying applications into production use. Classic CM—consisting of identifying system components, controlling changes, reporting the system’s configuration, and auditing—won’t do the trick anymore. Bob Aiello presents an in-depth tour of a more robust and powerful approach to CM consisting of six key functions: source code management, build engineering, environment management, change management and control, release management, and deployment. Bob describes current and emerging CM trends—support for agile development, cloud computing, and mobile apps development—and reviews the industry standards and frameworks that are essential in CM today. Take back an integrated approach to establish proper IT governance and compliance using the latest CM practices while offering development teams the most effective CM practices available today.      
 
Copyright © 2017 CM Best Practices. All Rights Reserved.
Joomla! is Free Software released under the GNU/GPL License.
 

Product News

Live Online Training

Jobs