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 ManagerAn 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 ManagerIn 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
SummaryThe 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.
30JANUARY, 2023 by Jane TemovTest Environment Management (TEM) is an essential process for ensuring the stability and consistency of the testing environment. It includes activities such as setting up the environment, monitoring and controlling the environment, and...
15DECEMBER, 2022 by Jane TemovDeployment planning is the process of creating a plan for the successful deployment of a new software or system. It involves identifying the resources, tasks, and timeline needed to ensure that the deployment is successful. Deployment...
12DECEMBER, 2022 by Jane TemovWhy CICD & TEM Goes Hand-in-Hand Continuous Integration/Continuous Delivery (CICD) and Test Environment Management are two essential components of a successful software development process. CICD enables teams to deploy new code...
08DECEMBER, 2022 by Enov8Enov8 is happy to announce the latest “evaluation”* edition is ready for consumption. *A complete Release & Environment Management product with a full license for 3 months. Our Release & Environment Management solution is designed to...
04DEC, 2022 by Jane TemovIf your organization is starting an agile transformation, you might be looking at it as an opportunity. Or perhaps you’re looking at it with some healthy skepticism. Either is understandable—or even both at the same time. The opportunity...
02NOVEMBER, 2022 by Sylvia Froncza Original March 11 2019An IT and Test Environment Perspective Traditionally, test environments have been difficult to manage. For one, data exists in unpredictable or unknown states. Additionally, various applications and services...