About Change management

[uppalasrila]

why do we use change management, and in which cases we use change and where should we create change like dev or prod like this, can anyone share a real time scenario

[GlideFather · Accepted solution]

ahoy @uppalasrila,

change is adding, replacing or removing something, it can be a new hardware or software.

Depending on the nature of that change it can be standard (pre-approved because it's happening frequently and is with low risks), emergency (reactive to some critical issue) or normal change.

for the normal and emergency changes there is a change advisory board to approve/reject such a change and it must be planned not to disrupt anything (after business hours, during weekend etc).

That's in a nutshell what change management does. Do you have any particular question about it?

[GlideFather · Accepted solution]

ahoy @uppalasrila,

change is adding, replacing or removing something, it can be a new hardware or software.

Depending on the nature of that change it can be standard (pre-approved because it's happening frequently and is with low risks), emergency (reactive to some critical issue) or normal change.

for the normal and emergency changes there is a change advisory board to approve/reject such a change and it must be planned not to disrupt anything (after business hours, during weekend etc).

That's in a nutshell what change management does. Do you have any particular question about it?

[Tanushree Maiti · Accepted solution]

Hi @uppalasrila 

Change management ensures that modifications to IT systems and services are executed safely, minimizing the risk of downtime or service disruptions. It controls the lifecycle of updates, tracks approvals, and ensures all changes are properly tested before reaching end-users

Why  Change Management?

• Risk Reduction: Assesses what is changing and how it might impact business users.
• Preventing Unauthorized Changes: Ensures no one modifies a system without proper documentation and testing.
• Compliance & Auditing: Creates a single "source of truth" regarding who did what and when.
• Stakeholder Communication: Keeps business leaders and end-users informed so they aren't surprised by unexpected downtime

Dev vs. Prod: Where Do We Create Changes?

Always we should only apply approved Change Requests in Prod. Never test brand new updates directly in Prod.

Refer:

Servicenow Doc: Change Management use case 

use case of change management 

Change Management in ServiceNow: Everything You Need to Know 

[Dr Atul G- LNG]

https://youtu.be/YNT-kaQOxDs