Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Test, deploy, release ... repeat

Matthew Heusser | Sept. 22, 2015
When it comes to release management, what sounds great in theory doesn’t always work in practice. Here are four steps to building an effective strategy.

Eventually the release process with get tight enough that it is time to improve something else. Wouldn't that be nice? 

Getting serious – what you'll do tomorrow 

While there are no standards for release management, there are some things that are common on many teams. For example, time spent on releasing the software is time that could have been spent developing it. Also, if the release process is expensive, it will make economic sense to perform it less often, which creates a delay in getting new features out to customers and allows the amount of change to increase. This makes every release riskier, which calls for more safeguards, which creates a longer deploy process, so it makes economic sense to deploy less often. The pattern is predictable and negative. 

Instead of doing what makes economic sense in the current conditions, ask how to change the system, and then move toward that change.

 

Previous Page  1  2  3  4 

Sign up for CIO Asia eNewsletters.