Implementing risk based release management

Teams and organizations that want to adopt risk based release management need to consider the following approaches:

Impact analysis

A good starting point is to invest in a tool that can visualize your system’s metadata dependencies. Such tools can help you perform proper impact assessment, document which metadata will have to be worked on as a result of the change, and properly estimate the technical risk.


Documentation tool

Most modern enterprises rely on multi-cloud, multi-system architectures to support their business operations. While there are dedicated tools for popular solutions (like Salesforce) to help understand technical dependencies, they is little such support for custom, legacy or smaller platforms.

This means that your ability to understand the interconnected network of metadata, regulatory compliance and operational process dependencies is dependent on curating a central documentation hub where these connections can be documented.



Central process library

By curating a central business process library you make it easier for yourself to keep track of all business operations using different systems or bound by specific regulations. You can learn more about the power of business process mapping in our dedicated course.



Release management system

Risk assessment needs to be actionable. You need to invest in a management system that will allow you to:

  • Classify risk of individual work items / tasks / stories
  • Classify risk of different releases and help you plan their scope accordingly

⚠ Action: click on the images below to enlarge them