The Hats of Release Management
Client: “Well first the Test Manager raises a CR for a new Release and then this guy here runs Jenkins to create a package and then we do [this and that blah blah blah]” Enov8: “Mmm! Ok you kind of described a Change Request followed by a Deployment. However, I was thinking somewhat broader. I was wanting to understand how your organization would manage a Portfolio or Quarterly Release. And I’d assume the process you described is not that?”There was some “Umms & uhhs” and then I realised that they had organised a meeting with engineers responsible for deployment. The kind of guys that might use a uDeploy, Bamboo, Octopus, or Electric Cloud. Essential roles, yet not the ones I had necessarily expected in this meeting.Mmm … my bad! … time to change the purpose of this workshop.To be fair, it didn’t impact me or the client too much, as our solution crosses the whole release spectrum, of which “Enterprise Release Management” is just one facet. However, perhaps next time I am a little clearer on my audience and expectations.So, with that in mind, what are the roles & responsibilities of Release Management?If I was to look at the Release Management Spectrum I can clearly spot 2, potentially 3 roles.
- The Enterprise Release Manager
- The Deployment Manager
The role of the Enterprise Release Manager
An overarching role typically focussed on moving enterprise changes into production. Or the person responsible for the Agile Release Train.Day to Day Responsibilities:- Enterprise Release (Portfolio) Scoping
- Pre-Release Communication – Advertising the broader purpose of the release & ensuring leaders are aware.
- Release Registration i.e. Project Onboarding – Define phases / stages – Define activities to be completed in each phase – Define milestones & stage gates
- Demand & Contention Management Note: Typically, in conjunction with Test Environment Management
- Enterprise Release Calendars (big picture communication)
- Enterprise Release Tracking / Performance Measurement
- Enterprise Release Risk Management
- Status Accounting & Reporting
- Post Implementation Reviews for Lessons Learnt & Continuous Improvement
- Enterprise Release Governance Strategy
- Promotion of Deployment Standards – Implementation Planning – Roll Back Planning
- Stakeholder Management – Stakeholders across the IT community and include Dev, Ops, Test & Project Managers.
- Ability to manage up & manage down – Enterprise change impacts the business and the key executives.
- Solid ITSM experience – Release & Change are core to ITSM best practice.
- Solid Project Management experience – At the heart of ERM is master scheduling & tracking.
The role of the Deployment Manager
In my opinion the heart of effective DevOps & CICD (Continuous Integration / Continuous Deployment). A relatively hands-on and technical role and potentially a very technical role as you endeavour to automate everything across your system stack.Day to Day Responsibilities:- Source Version Control, Branching & Labelling – Although may fall under the Software Configuration Manager.
- Build Management, Unit Test & Packaging – Ideally fully automated.
- Definitive Software Library / Release Repository – Establishment of ‘source of truth’ (SSOT) to promote both promotions & rollbacks.
- Deployment / Implementation Planning – Ensuring that tasks are communicated, coordinated & ideally standardised.
- Deployment Automation – Promoting streamlining and reduction in manual error.
- Shakedown – Ensuring target solutions are still operational & healthy. – Ideally using End to End Test Automation (aka Test Synthetics). Note: Often passed to the Test Environments and/or Test Automation team.
- Promotion of Build Standards & Automation
- Promotion of Deployment Standards & Automation
- CICD Strategy
- Broad Technical Skills -Enjoys getting hands dirty and not scared of the Environment Stack (Apps, Data & Infra).
- A Team Player – Working closely with different delivery teams e.g. Engineers, Developers & testers.
- Solid Software Engineering experience
Summary
The above was just a glimpse at the two types of “release management”, however every organisation has its nuances and expect to see different titles, responsibilities and some overlaps.If I was to explain it as simply as possible, however, I’d offer this:- Enterprise Release Managers are focussed on delivering organizational change at scale.
- Deployment Managers are focused on tribe/team activities and rapid system change.
Relevant Articles
Environments: The ROI of TEM
16September, 2021 by Carlos SchultsLet me start with a question: as a leader in tech, are you satisfied with the budget you have? If I had to guess, I'd say the answer is no. Because of that, calculating the return on investment of the many activities in software...
Release: The Benefits of Deployment Planning
14AUGUST, 2021 by Ukpai UgochiIt is the goal of every software engineer and software development firm to continuously ship products to end users. This can only be achieved through software deployment. In this post, we'll explore deployment and deployment planning,...
Containers – The Essentials
09SEPTEMBER, 2021 by Eric GoebelbeckerLet’s talk about container essentials. Over the past few years, containers have transitioned from the hottest new trend to essential IT architecture. But are they are good fit for you? Are you wondering whether or not you’re using...
Environments – Monoliths Versus Microservices
05AUGUST, 2021 by Alexander FridmanIn the beginning there was nothing. Then there was the monolith, though we used to simply call monoliths "software." Today we have two rival architectural types: monoliths and microservices. This post will explain what monoliths and...
What Is Your Attack Surface?
15JULY, 2021 by Justin ReynoldsCompanies go to great lengths to protect their physical environments, using deterrents like locks, fences, and cameras to ward off intruders. Yet this same logic doesn’t always translate to digital security. Corporate networks — which...
Data: What Is DevSecOps?
06JULY, 2021 by Justin ReynoldsCompanies today face increasing challenges around reducing the time and cost of software development. Many are thus using DevOps methodologies, which combine software development and IT operations to achieve continuous delivery and...
