Benchmarking Release Management
by Niall Crawford
“It goes without saying, that the backbone of all organizations today is digital and independent of the end-products you provide”.
Digital the Backbone of Business
It goes without saying, that the backbone of all organizations today is digital and independent of the end-products you provide, there is an inherent need to drive your features and solutions from conception (the initial idea) through to production (the end customer) as quickly, safely and efficiently as possible.
- That is, every organisation requires effective IT Release Management.
So, what is IT Release Management? Let us start with a definition (or two):
Release management is the process of managing, planning, scheduling and controlling a software build through different stages and environments; including testing and deploying software releases.
Enterprise release management is a multi-disciplinary IT governance framework for managing software delivery and software change across multiple departments in a large organization.
The former is what a DevOps engineer might gravitate to i.e. someone with the task of building and deploying code to their individual system or services.
And the latter something that might be handled by an Enterprise Release Manager (or Portfolio Manager), that is someone interested in coordinating a family of system/project releases using methods like SAFe (Scaled Agiile Framework) “Agile Release Trains” to maintain collective velocity, phase alignment, and a unified implementation.
A Visual Definition of Release Management
Alternatively, consider the following diagram.
Holistic Release Management is a combination of Vertical Practices responsible for supporting delivery through the system lifecycle (i.e. Analysis, Design, Development, Test, and Implementation), a set of Horizontal Practices responsible for driving transformation across the enterprise (or divisions).
Measuring Release Management
Independent of whether your perspective is vertical (system focused) and/or horizontal (enterprise focused), there is little argument in the importance of getting both activities completed correctly and having the various teams working together as effectively as possible.
However, agreeing on benchmarking may not be trivial as the two tasks, although obviously related, are quite different. With the above in mind, we decided to put together two sets of release metrics that we thought would be useful in providing insight with respect to current release behaviour and capability.
- The ten best metrics for Enterprise Release Management (ERM)
- The ten best metrics for Release Management (aka System Deployment)
Note: Special thanks to some of our enov8 customers for sharing some of these.
Enterprise Release Management (ERM) Metrics
Whom: Typically, the responsibility of an IT Enterprise Release Manager the main goals are to ensure that a family of project releases (changes), which are often related and contain dependencies, can move through the software development lifecycle, from conception to production, in a controlled and aligned fashion.
Key data & trends, to be captured would be:
- Size of Enterprise Release by Projects (Project Releases Registered)
- Size of Enterprise Release by System Deployments
- Size of Enterprise Release by Features (or Stories)
- Project Releases Status (Success/Failure)
- Project Releases Delivered on Time
- Project Release Delay
- Number of Project De-Scoped*
- Number of Systems De-Scoped*
- Number of Features De-Scoped*
- Root Cause of Project Release Delay
*Note: In ERM, de-scoping is most typically caused by a project failing to meet its release gate obligations and being removed from the enterprise release as quickly as possible and thus avoid an impending “train crash’.
Release Management (System Deployment) Metrics
Whom – Typically, the responsibility of a DevOps “System Release” Engineer, the main goals are reliability and velocity i.e. the engineer wants to get the job done as safely and quickly as possible.
Key system deployment data & trends would be:
- System Deployment Frequency
- System Deployment Feature (Story) Size
- System Deployment Status (Success/Failure)
- System Deployment Time (ideally versus SLA)
- System Deployment Outage Time (outage time for deployment itself)
- System Post-Deployment Outage Time (outage caused by unsuccessful deployment)
- System Post-Deployment Incidents (Tickets) due to a deployment
- Mean Time to issue detection
- Root Cause of System Deployment Issue (Delay, Incident or Outage)
- Mean Time to remediation
Note: In the case of DevOps you would expect these metrics to be of use across the lifecycle. Therefore, the word ‘System’ could quite logically be replaced with ‘System Instance’, where you would have Instances in Integration, UAT, Staging & Production.
Food for thought
Hopefully, you found some of the above release metrics useful & maybe thought-provoking.
Ultimately metrics need to be aligned with your own operating model.
However, in closing we’d say this:
Good release metrics should always do the following:
- Clarify release strategy i.e. direct good practice
- Understand existing release capability i.e. strengths & weaknesses and
- Drive release enhancement i.e. continuous improvement
What else would you add to the above “Release Management” Metrics?
- Understand the association between ERM & DevOps:
- Releases need Environments, Non-Production Environment Metrics:
Learn More or Share Ideas
If you’d like to learn more about Release Management or perhaps just share your own ideas then feel free to contact the enov8 team. Enov8 provides a complete platform for addressing organisations “DevOps at Scale” requirements. Providing advanced “out of the box” IT & Test Environment Management, Release Management and Holistic Data Management capabilities.
Niall is the Co-Founder and CIO of Enov8. He has 25 years of experience working across the IT industry from Software Engineering, Architecture, IT & Test Environment Management and Executive Leadership. Niall has worked with, and advised, many global organisations covering verticals like Banking, Defence, Telecom and Information Technology Services.
Do you ever wonder why the environment preparation or releases take so long? After all, the company just invested “zillions” on a whole bunch of great tools and a cloud framework.
So, you have decided you’re going to implement a Scaled Agile Framework (SAFe) and promote a continuous delivery pipeline by implementing “Agile Release Trains”…
I am continually ‘un-amazed’ when I go into large organizations and look at their ‘DevOps’ strategy. At a team level, it’s invariably no different to what we were doing back in the late 90’s…
The intention of environment synthetics is to provide ‘high-level of confidence’ applications (your system instances e.g. UAT Home Loan System) and their underlying component services…
DevOps & DevOps at Scale is little a bit like comparing the building of Sand Castles on a Beach to Town Planning. Here are 5 practices to promote as a way of preparing for a DevOps at scale capability…
This year’s world quality report (2018) has once again identified Test Environment Management as a major challenge for Agile Development & Testing. Key statistical insights from this report included…