With increasing adoption of agile methodology and the growth of dynamic requirements creeping into the scope – the focus of release management has increasingly shifted towards short , iterative and incremental release of software .
While the visible benefits of short and incremental release of software are easily felt , there are many hurdles that can haunt the development and management teams from reaching the goal .
The below forrester report on global online IT release management survey gives some clear insight on the grey areas of the release management process .
Top-3 things that need better approach to make release environment agile ready are discussed below .
- Shorter and iterative release cycles make sense if the impact of regression after a release is less.
If most of the time the development teams spend time in fixing the issues of the previous releases arising out of regression [something that was working in release 1.a is not working in release 1.b]
The key to this is to have higher levels of automation in-place. No better solution than this.
In the report 65% feel that they are not happy with level automation rating <= 5/ 10 talks about the internal frustration of development teams doing same things again and again manually is visible.
- Reliability gives us another shocking stat and a cause of concern with close to 46 % people are not sure when the release that make on a giving will be really smooth and teams afford to have a peaceful sleep on the night of release.
- The quality parameters , tooling used and the process followed in release of the software is also not perceived well with close 45% of people [ ~~ 1 in every 2 members ] who know the depths of release process are unhappy with the release quality .