Change Management

PrudhviDeeK
Tera Contributor

3 weeks ago

I want to learn Change Management from end to end comprehensively.. What are the sources?.Can anyone please provide me with relevant sources?

Labels:
0 Helpfuls
  • 566 Views
7 REPLIES 7

Aditya_hublikar
Kilo Sage

3 weeks ago

Hello @PrudhviDeeK ,

 

You can refer this threads:

 https://www.servicenow.com/community/itsm-forum/change-management-in-servicenow-everything-you-need-...

 

https://www.servicenow.com/community/itsm-articles/change-management-process-workflow/ta-p/2299141

 

 

If this helps you then mark it as helpful and accept as solution.

Regards,

Aditya

0 Helpfuls

Aditya_hublikar
Kilo Sage
In response to Aditya_hublikar

3 weeks ago

Hello @PrudhviDeeK ,

 

I hope you are doing well . Does my response helps you ? 

 

 

If my response helps you then mark it as helpful and accept as solution.

Regards,

Aditya

0 Helpfuls

yashkamde
Kilo Sage

3 weeks ago

@PrudhviDeeK  - Some bullets which might help you better grok it:

  • Change Management is a fairly abstract thing. It's merely a useful tool that can be applied to many domains (i.e.: like version control).

  • Changes exist to document execution of a process as it unfolds. Changes are to change management as Incidents are to incident management.

  • IMO, the value of Change Management comes from...

  • The fact that the change is documented as it happens. Much like Incidents, this live documentation approach is great for CYA and maintaining accountability.

  • The ability to put guardrails on processes. The value here is pretty obvious vs. a paper process, I think. Humans make mistakes, particularly when they're in a rush -- the machine never forgets!

  • The ability to report on Changes and spot macro trends when it's time for process improvement

  • Some examples of things Changes can be used for tracking...

  • The process of doing maintenance (e.g.: a software/hardware upgrade on a server)

  • The process of changing vendors for an API

  • The process of changing other processes within the organization (AKA: Organizational Change Management)

 

-> Also with these there are a lot of moving pieces with change.

We have CAB meetings twice a week to let everyone know what’s going on.

The day before CAB, a scheduled report goes out showing the outstanding changes that need movement or they will not be on the agenda (not fully approved, in implement but not moved to review yet, etc).

During CAB the change manager runs the show and updates CRs as needed through the CAB interface.

Actual work on CRs is varied. Some groups use tasks to ensure all parts of a CR are completed, esp when the work is sequential and across different teams, or if something requires verification. A CR cannot be put into review status until all tasks are completed.

And then, we have rules around normal, standard and emergency changes.

 

 

If my response helped mark as helpful and accept the solution

0 Helpfuls