We live in an age of constant change. We tend to associate the idea of change with that of progress, and while this is not necessarily always be the case, every "change for the better" obviously requires a change.
However, it is common to come across IT service managers whose motto is still: "if it ain't broke, don't fix it". And although it is true that changes can be a source of new problems, and changes should never be made gratuitously without evaluating their consequences properly, it can be much more dangerous to become stagnated in out-of-date services and technologies.
The main reasons for making IT infrastructure changes are:
- Solving known errors.
- Developing new services.
- Improving existing services.
- Meeting legal requirements.
The main aim of Change Management is to evaluate and plan the change process to ensure that, if a change is made, it is done in the most efficient way possible, following the established procedures and ensuring the quality and continuity of the IT service at all times.
The interactions and functionalities of Change Management are briefly summarised in the following interactive graphic: