Application Release Management

APPLICATION RELEASE MANAGEMENT CAN BE CHALLENGING

Poorly designed release management processes will often force IT resources to spend a significant amount of time troubleshooting problems and managing complexity. It regularly also affects the environment and degrades services.

A best practice Application Release Management approach should include at least the following key objectives:

  • Ensure integrity of the release or change set and its included components is maintained throughout the delivery process
  • Ensure all release or change sets can be tracked, installed, tested, verified and/or rolled back if required in a consistent, repeatable fashion and are stored
  • Ensure that any changes are managed during the delivery process
  • Ensure all release or change sets can be delivered at the “speed of business”
  • Ensure transparency, insight, and stakeholder communication in the end-to-end process

Depending on type of business or application, 2 main release approaches exist:

top-down-application-release-management-graphic
botom-application-release-management-graphic

 

Clarive is designed to support the bimodal enterprise and supports both
top-down and bottom-up release management!

Use of cookies

This web site uses cookies to give you the best user experience. If you continue browsing you are giving your consent for the acceptance of the aforementioned cookies and the acceptance of our cookies policy, click at the link for more information.