Change Management:

In system’s engineering, process of CM is to attend change request from client, determining attainability in system, organizing, development and testing the changes that we have made in a system.

After successful testing, we must make sure that we are creating Change Proposal document with additional effort quotation and get it signed by Authorised Personnel from Client Side before to starting to implement it in the product.

Once it is signed off, then go for implementation, validate/test the changes in the system and launch the system and close the process.

Why to Make Changes:

No matter how much correct, you’re documenting the requirements, users/ stakeholders will find something is missing from the process they stated or there is an improvised way of achieving desired target.

Sometimes we need to add some new features to enhance the available system, then we need to opt for CR.

Business Remodelling: Sometimes Businesses needs to reorganize their structure in that case CR received.

To fix errors/ bugs.

To integrate new equipment into existing system or to add new feature or to reduce cost by reducing human resources it can make existing system powerful for less errors and to achieve more success.

Who is Responsible for Changes:

Stages of Changes:

  • Unfreezing:
    • It means Accepting the change and being open for participating in the process.
  • Changing:
    • Being a part of Change Process.
  • Freezing:

In this phase you have cooperated in Change Management Process and learned about the new procedure.

How to Reduce Changes:

When we are developing any system, we must make sure we are gathering requirements correctly using Multiple combinations of available Elicitation Techniques from its stakeholders to avoid receiving change requests.

How to deal with changes:

Once, received the change request prepare the CR document, do the feasibility study and prepare the quotation for an effort those needed to implement changes. Get it signed by Client and approve the quote then start developing the changes in system.

Need to understand the reason for change because if it is not mandatory, we can reduce it from scope of work. Also, we need to look for result that we are going to achieve using this change, then we can check for alternative to achieve the desire result.

Understand the risks involved, as we are going to change portion of codes and going to improve it search for the dependencies between the results generated by each function and develop accordingly.


How to evaluate Change Management Process:

When we are in CM phase we have to keep on evaluating our system as it will help you in keeping track of what’s working, what’s under development and what is yet to be developed and what will be next. Also to achieve these answers, we need to ask ourselves some questions like:

  • Are we achieving the goal?
  • What does the feedback says?
  • We will deliver it on time?
  • Are we sticking to the budget?

Asking questions like this, will keep us on track to achieve the desired state of the system.

How to keep a Track of Changes:

There are several ways to document and track the changes that needs to be done in the system. Some of them are:

  • Walkme
  • Remedy ITSM 8.0
  • ChangeGear
  • SpiceWorks 5.0

About Tejas Chintamani

Check Also

Q2. What are project priorities? Why this is important? How to handle this?

Project prioritization is the process of determining which projects are the most important and the …

Leave a Reply

Watch Dragon ball super