Differences Between Configuration Change & Release Management

Configuration change and release management demand computer skills.

An organization's top executives pay special attention to corporate operating systems, including new application development procedures in the short and long terms. Configuration change and release management are key steps in operating systems management.

Configuration Change

Configuration change consists of the tools, procedures and methodologies that software engineers and other information technology specialists use to change general or specific attributes in operating software. According to Microsoft, central in configuration change steps are scripts and procedures necessary to keep track of application versions.

Release Management

Release management includes steps required to review and monitor the effectiveness of new applications after implementation. Microsoft indicates that release management procedures typically require script-based installations and script organization. These installations provide easy ways to catch errors and include clean, clear and independent installation procedures.

Relationship

Configuration change and release management are distinct activities in a firm's operating systems management processes. However, both concepts may interrelate, depending on business requirements. For example, a company's chief information officer may direct a configuration change coordinator and release management specialist to advise whether the company should upgrade existing software or purchase new applications.

References

• Microsoft Corporation: Change, Configuration, Release Management