Work in the project world? Learn these ITSM Release Management terms – By Alok Das

Change Managers, do you understand these key terms in ITSM Release Management?

You might have heard your Business Analyst or Programmer colleagues often referring to these terms.

Release Management:

• Involves managing, planning, scheduling, and controlling a software build through different stages and environments, including testing and deploying software releases.

Release:

• Is a collection of hardware, software, documentation, processes, or other components required to implement approved changes.

Deployment:

• Refers to the activities necessary for preparing the new or changed services and components for operational use.

Release Plan:

• Is a document detailing the schedule, resources, and activities necessary to deliver a release to production.

Change Management:

• Is a process that ensures all changes are handled in a structured manner to minimize the impact on services. Alert: Don’t confuse this term with Organisational Change Management.

Rollback:

• Is a plan or method to return to a previous version if the new release causes issues.

Build:

• Is the process of compiling all the components of a release into a working product.

Test Environment:

• Is a controlled setting where releases are validated before moving to production.

Configuration Management Database (CMDB):

• Is the repository that stores information about all components of the IT environment.

CI/CD Pipeline (Continuous Integration/Continuous Deployment):

• Is a series of automated processes for integrating, testing, and deploying code changes, ensuring faster and more reliable software releases.

Change Advisory Board (CAB):

• Is a group of stakeholders who review and approve proposed changes, ensuring they align with business objectives and minimise risk.