Skip to main content

The Difference Between Change and Release Management

A reader recently asked me to comment on the difference between Change and Release Management. The first question “is it a request or proposal?” is a good one.  When we use the term proposal, normally we are speaking about major changes that will involve significant risk, cost or organizational impact.  Proposals are normally initiated by the portfolio management process.  They can also be submitted by a program or project management office.  Again remember that each organization is unique and how they do this and at what level it takes place can be different from organization to organization. This is defined at a high level, but the details necessary will depend on the organizational requirements. 

For the most part before the new or significantly changed service is chartered it is critical that the proposed change be reviewed for its potential impact on other services, shared resources and the change schedule. These proposals are submitted to change management before being chartered so the service provider can identify any potential conflicts for resources or other issues.  Authorization of the proposal does not immediately mean approval of implementation, but allows the proposal to be chartered so that service design (infrastructure, services or development (software) activities can begin.  These proposals should include, a high level description of the new or changed service, including any business outcomes to be supported and the utility and warranty requirements. A business case which will define risks, identified issues, alternatives, as well as the budget and financial expectations. Finally it should have a schedule for the design and implementation of the change.  Remember that we must be agile in our thinking and as we move forward and gain information and knowledge these items can change over time.

Once the proposal has been reviewed by change management and all issues or potential conflicts have been accounted for, the proposal will be authorized and the change schedule can be updated to include implementation dates of the proposed change.  After the change is chartered, RFCs will be used in the normal way to request specific changes.  Within the RFCs we will begin to define items at the CI level and technical details will be defined and documented. 

Although ITIL is a waterfall methodology it doesn’t mean that there can’t be connections back and forth between design and transition.  Remember there are very tight connections between change, release and deploy and that some design and all building and testing happens within this space.

Deployment is handled within the four phases of release and deployment.  Change management authorizes release and deployment to move forward as specific criteria gets met. In general change management authorizes release and deployment planning (phase1), authorizes release build & test (phase 2), check into the DML (phase 3) and then finally the deployment (phase 4).  Of course at the end of deployment we will do a post implementation review (PIR) for lessons learned.

For additional information please see the ITSM Academy's ITIL portfolio: www.itsmacademy.com/itil


Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th