Configuration Management Change Request

Configuration Management Change Requests are accomplished through the strong relationship between Configuration management and Release management, Change management.

Configuration Management Change Requests – Configuration / Change relationship

Change Management, describes procedures for authorizing and implementing IT infrastructure Changes. Typically we find that there are organizations who treat these two processes separately.

However, I am going to get on my soapbox here and tell you they must be treated together, that is, they are not the same process but they have such a strong relationship that you really cannot have one in your organization without the other and call it effective!.

Now of course they are separate processes but the fact of the matter is that everything within the CMDB is subject to Change Management. And that is where a lot of organizations go wrong

Configuration Management Change Requests – Is Release management really party of change Management?

Release Management can be regarded as part of Configuration Management. It covers the building, distribution and implementation of Releases. This process covers, in general terms, the procedures required for controlling software, hardware and documentation and the update of the logical model of the IT infrastructure.

The logical model is used to control and record the details of the building, Release, distribution, implementation and maintenance of Releases.

Well, when you really get down to it a single Configuration Management system should be used to control components in both the live and the development environments.

If there are multiple platforms, the live Configuration Management system should be designated as the 'master' and links defined to the development control and build tools in order to control the movement of components into and out of independent testing environments.