Accelerated Time to Market Value Driver
Average Release Duration
Deployment Frequency is one of the 4 key DORA metrics. Average release duration tracks the time between your releases over time and the overall reduction you’ve achieved, which is essentially the deployment frequency.
The metric card shows the # of FTEs freed over the given date range (on average), calculated based on the number of manual hours saved through automation.

As Provar Quality Hub has a bi-directional integration with JIRA, this allows us to import and sync Projects, Epics, User stories, Bugs, Releases, and other issue types in our application. This enables Provar Quality Hub to surface key insights from data synced over from Jira natively!
The metrics drill-down shows additional information, highlighting the release durations over time, key insights on release data, breakdown of release stage timings, maturity information, and steps to reduce your release cycle time.

The How to Improve section might include information on key changes in your release process, tips to streamline your deployment pipelines, or suggestions on specific feature accelerators, such as Feature Flags for “ghost-style” releases.

Each tip/suggestion will also come with an estimated impact that you can directly monitor over time and implement with your team to further improve your Salesforce release process.
Test Cycle Time Reduction
This metric helps to track the overall improvement in your testing time with Provar. One of the key benefits of Provar is reduced time spent testing through the adoption of test automation. This key metric allows users to track their overall test cycle time and how they’ve reduced the overall time spent testing each cycle.
The metric card highlights the % reduction in test cycle time (using the starting date as the baseline) across the given date range, an insight on the starting point and current cycle time, the maturity tier, and the overall goal to maturity tier 4.

Initially, the cycle time would be expected to be longer than desired. Over time, with the adoption and optimization of Provar, the total amount of time spent testing will naturally decrease each release cycle, resulting in faster validations for each release/deployment.
The metric drilldown will allow you to see this cycle duration over time, key insights on your reduction stats, a breakdown of time savings, current cycle time, and steps to improve your testing cycles further.

One of the key insights may give leadership valuable information, such as the ability to free up resources for additional exploratory testing. Another insight could be that more rapid testing enables more defects earlier to be caught in the development cycles, promoting shift-left testing.
- Home
- How to Use Quality Hub
- Actionable Insights
- Quality Hub Setup
- Quality Hub Setup and User Guide
- Installing/Updating Quality Hub
- Configuring Quality Hub
- Setting Up a Connection to Quality Hub
- How to Know if a File in Automation is Linked in Provar Manager
- Uploading Existing Manual Test Cases to Provar Manager with DataLoader.Io
- Object Mapping Between Provar Automation and Provar Manager
- Provar Manager Filters
- Metadata Coverage with Manager
- Quality Hub Integrations
- Plugins
- Release Management
- Test Management
- Test Operations
- Release Notes