Skip to main content

VOI and ROI of Release and Deployment Management

I was recently asked about the ROI and VOI of Release and Deployment Management. 

Let me start by acknowledging that there is a lot of confusion about the difference between Release and Deployment Management and Change Management.    Change Management is a risk management, governance process.    Release Management is more actionable – it is about bringing one or more changes to life through defined pre and post production activities.  

You could almost call it the DevOps process.

The growing requirement for rapid (some would say continuous) deployment does not undermine the need for quality releases.    In fact, a structured approach to rapid deployment is more critical than ever since there is less time to flush out errors.  You can make the process more agile by building release models for different types of releases.  The models can match the rigor associated with building, testing, implementation testing and deployment with the complexity, risk, business need and impact of what is being released.    The model will also address  the need (or lack thereof) for documentation, early life support, user preparedness and communication.  

Essentially, an individual release model will pre-define what needs to be done by both Dev and Ops for this specific type of release.   As time goes by, the models may be a critical success factor in instilling an agile DevOps culture into your environment.  Release and Deployment management is not bureaucratic by design – so go ahead and build some different models for common types of releases and test them out. 

Here’s the VOI and ROI  - failed changes and releases are very expensive and in some environments the damage could impact human life, market perception and/or loss of customers.  With just about everything moving online – whether via the cloud or through traditional web services – the need to be able to “drop code” multiple times a day will continue to increase.  Dev and Ops will need to cross the cultural divide, perhaps using release models as the bridge.  Someday, this process may be as significant to DevOps as Incident Management is to the Service Desk.


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

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

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