Our software development process primarily uses Adaptive Test Management for Jira to monitor real-time risks across all stories and sprint planning. Additionally, we use it to create action plans for high-priority risks.
Its valuable features include the risk count feature, which helps us track how many projects are at risk or not at risk. Another feature is the risk metrics, which allow us to understand and communicate how risks are distributed by viewing them on both the X and Y axes. Additionally, the add-on configurations are very flexible, letting us define risks in a way that suits our needs. These features are particularly useful for us.
The product's reporting and metrics capabilities are useful for our project management. From a reporting standpoint, we get updates on a weekly or sprint basis, which helps us track how many projects are at different risk stages and who is responsible for what. This provides a high-level view of our progress during sprints and at the epic level, especially if an epic spans multiple sprints or quarters. We can also export these reports into PDFs and other formats, which is handy. As for metrics, we don’t track metrics separately because the reporting gives us the insights we need to understand performance and decide on the next steps.
It’s difficult to pinpoint cost reductions directly, as the impact on costs is more of a long-term effect. However, Adaptavist Test Management for Jira has been beneficial in other ways. The dashboard and reporting features help us identify and address red flags, providing a proactive view of potential challenges before they become issues. Previously, we would deal with problems as they arose, but now we can anticipate and manage challenges more effectively.
