Changes v's Releases

[vawns]

Hi All,

I’m looking at making some improvements in my current Change Management process and part of this will review the relationship with Release Management and specifically what constitutes a Change versus what constitutes a Release.

I would love to know how other organisations make the differentiation, how do you decide what’s a change and what’s a release and how do you manage the relationship between the two.

Any help or feedback would be gratefully received

Many thanks & best regards,

Vawns

[Ed]

Hi vawns

for me it is quite simple

A Change is a Request For any alteration to any service, hardware, software, etc. etc. hence RFC - Request For Change

A Release is what puts that Change into the Live environment after risk assessment, testing, and authorisation.

Regards

Ed

[jpgilles]

If it can help:

Change management is basically related to the project phase from early identification of needs or requirements up to the testing of the solution.

Release management is about preparing, planning, and implementing the change.

The relationship between Ch M and RM is not 1 to 1:

A change can be implemented through several releases (or versions)
A release can integrate several changes

br
JP
_________________
JP Gilles

[Guerino1]

Hi Ed,