LF

Enterprise Release Management – The Bridge between Corporate Strategy & DevOps

13

OCTOBER, 2017

by Niall Crawford

According to Wikipedia, Enterprise Release Management (ERM) can be defined as:

A multi-disciplinary IT governance framework for managing software delivery & software change across multiple departments in a large organization. ERM builds upon release management & combines it with other aspects of IT management including Business IT alignment, IT service management, IT Governance and Configuration management.

However, I’d like to describe it slightly less verbosely, or more simply.

  • Enterprise Release Management is the “Bridge between Corporate Strategy & DevOps”.

At enov8, we see ERM as the single overarching governance mechanism for bringing digital-change from cradle (i.e. executive stakeholder conception) to grave (i.e. production deployment).

A solution that ensures the corporate needs of the business are understood, prioritised and scoped and ultimately follow a controlled path through the various phases of the IT delivery lifecycle (including resource management, development & test) and ultimately into production itself.

Referring to the above ERM Use Case, the key activities & actors involved in ERM include:

  1. Defining the key business objectives i.e. goals for next period
    Whom: Key Stakeholders e.g. CxOs, business executives & strategists
  1. Articulating these business objectives via an enterprise release plan
    Whom: Senior IT management, enterprise release (or portfolio management)
  1. Identifying (scoping) the discrete projects that will achieve these release outcomes
    Whom: enterprise release & project managers
  1. Establishing key milestones for these projects to ensure cross team alignment & tracking
    Whom: enterprise release & project managers
  1. Establishment of gates to ensure that each project meets necessary delivery objectives
    Whom: enterprise release & project managers
  1. Identify the key IT resource (including system) to ensure readiness & avoid contentions
    Whom: enterprise release, project managers, test environment managers & system owners
  1. Development & Test Phase Planning
    Whom: project managers, solution delivery managers, test managers
  1. Implementation (Deployment) Planning
    Whom: project managers, test environment managers & deployment managers
  1. Release Operations (Scheduling & Engineering)
    + Including Streamlining via standardising & automating build, package, deploy & test.
    Whom: project managers, solution delivery managers, test environment managers & engineering
  1. Deployment / package tracking
    Whom: test environment managers & configuration managers

About enov8: Enov8 are a world leading Test Environment Management & Enterprise Release Management solution provider. Our philosophy is to help organisations be “Agile at Scale” through a combination of helping enterprises understand and manage the big picture and ultimately marry that with the necessary IT delivery activities.

The Enov8 Release Management solution is an “extensible engine” that supports the complete release management needs of an organization, independent of chosen lifecycle e.g. Agile or Waterfall. This includes scoping the release portfolio, through to project level planning, cross project alignment, deployment planning and release execution (both manual & automated).

Learn more about our ERM solution: https://www.enov8.com/enterprise-release-management/

 

 

 

 

 

 

 

 

Relevant Articles

IT Environments – Top 5 Deployment Metrics

03 February, 2019 By Christian Meléndez. Preamble: Following on from our previous blog on Enterprise Release Management bench-marking, Christian talks about the “sister disciple” of deployment management and more specifically the top 5 metrics one could use to better...

IT & Test Environment Management Anti Patterns #2 – Containers

29 JANUARY, 2019 By Sylvia Fronczak.   Anti-patterns often arise when developers find creative or outside-the-box uses for a technology - or when they find workarounds for limitations that were specifically put in place by the creators of the technology to prevent...

IT Environments – Why Use Microservices?

08 JANUARY, 2019 By Eric Goebelbecker. New technologies and new ways of doing things are continually impacting the way our IT Environments evolve and how we do things. One area of growing popularity is Microservices.   Why Use Microservices? Why should you start using...

Why DevOps Fails: A Closer Look

09 DECEMBER, 2018 by Sylvia Fronczak DevOps promises greater innovation, speed, and automation—along with a more engaged and motivated team. With this list of benefits, many organizations are working to bring DevOps to their teams. However, with all the companies...

Test Environments – Why Containers?

22 OCTOBER, 2018 by Eric Goebelbecker Containers are nothing new. Depending on how you look at it, you can make a case for them being around at least since 1982. But since the introduction of Docker in 2013, they’ve enjoyed a surge of popularity. Why? In just a few...

Why Cloud “Server” Tagging Strategies Are Important

15 OCTOBER, 2018 by Christian Meléndez Preamble A key part of Enterprise IT Intelligence is understanding you Cloud Resources. And where better to start than using the "elegant" concept of Tagging. A concept used across the various cloud and infrastructure management...