Release Management amplifies the effects of your change process (good or bad)

Let’s generalise for a moment. Release management usually comes into effect in two significant circumstances:

1. When you want to bundle changes into a package

2. When you want to fully ‘transition’ a service into operation and deliver the associated support and knowledge etc

In both of these circumstances, the output of the release will be an amplification of the inputs, ie. the component changes.

If your change management process is shaky, the release will be hard to build, test and deploy (ignoring all of the other organisational and political issues you may encounter).

But if your change process is solid, if the component changes are of good quality, then building testing and deploying your release becomes that much easier.

So if you get asked to implement release management, the very first thing you should do is find out how solid the change management process is, because when it comes to change and release, garbage in = garbage (squared) out.