In every company now, nowadays, the role of computer is absolutely central. In fact, even for companies that do not directly produce software but use it to support its core business, the provision of programs is an asset to be preserved, as well as to increase, to stay current and competitive. And one of the key moments of the so-called cycle of the software life is definitely one dedicated to its maintenance . What in computer jargon is known as Change Management. In this guide, we see just how to organize change management within a company.

I mentioned in the introduction that a program, once purchased and then introduced into company , does not have to remain true to itself indefinitely. It can highlight the need for corrections in the case revealed errors in performing certain people certain activities . Or, and this is perhaps the most frequent case, the original program must undergo an upgrade, often urgent, if it proves missing some features, sometimes essential to the continuation of the corporate mission.


For example, if the state imposes, through its law, new obligations (fiscal, administrative, etc.)., it is immediately applied to the information system of the company to plan accordingly, through new developments in software . In all cases, the information assets undergoes a need to update and its management is defined precisely Change Management . In the case of corrections, it is called corrective maintenance , in the case of updates due to new application requirements, it is called adaptive maintenance .

To manage the maintenance and corrective and adaptive, which actually results, as anticipated, Change Management as a whole, you have to define in advance of the time windows in which you will install the software, jargon computer where it will be carried to its distribution, for example every Saturday night from 21 hours up to 24 hours.So you’re going so that all processing afternoon-evening concluded within that time, given that, at 21, will start the software updates you want.

Of course, all staff, both users and developers of programs of the same, must be aware of these deadlines and they have to adapt or to agree new ways of delivery. Remember always that in fact a computer program that never changes after a short period of time becomes quite obsolete.