Don't Relegate Release Management to a Product's Release


In his CM: the Next Generation series, Joe Farah gives us a glimpse into the trends that CM experts will need to tackle and master based upon industry trends and future technology challenges.

Release Management for Everyone
The above questions may be important to the release team, but they are also important to the development and support teams, as are dozens of other queries.  And not just at the release level, but for any build that is produced from the CM repository.

A developer finds a problem that wasn't there a week ago.  He needs to identify the changes that have gone into the code since then. The quality team wants to know why the problem wasn't detected earlier - is there a missing test case or was testing not completed?  Similarly if a developer finds a line of code that she doesn't understand, she needs to trace it to the reasons that it was introduced.

These examples require the same product information that the release management functions require.  Instead of comparing releases, developers are usually comparing builds.  Instead of identifying the full set of features, they want to know if their feature changes made it into the build.

It's the same ALM integration, the same traceability data, and the same process and the same data capture needed by the release process that provides key benefits to the rest of the team. So look at your release management more closely and when you have your tools and processes well oiled, you'll find productivity increases across the board.

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.