Skip to main content
System StatusContact Support
VersionOne Community

Continuum Flow - Progression Metrics

Overview

Implementing enhanced processes is the first part of a successful devops implementation; measuring the performance and impact of these processes will ultimately allow devops champions to gain unique insights and discover areas for improvement.

While progressions provide a snapshot of the current state of your value-stream and make the work visible, progression metrics provide historical performance of past releases and allow for comparison and analysis of how the introduction of certain practices impact the ability to deliver.

By measuring development & delivery activities, Continuum delivers key performance & risk indicators in a single place, allowing you to gain unique insights as well as identify areas of opportunity to continuously improve and deliver value to your customers faster.

Accessing the Metrics Dashboards

The data of the metrics dashboards is unique to each progression and thus located alongside it.

  1. Click "Progression Dashboards" on the homepage.

Homepage Dashboard Link

  1. Select the desired progression from the drop-down list. 

The following filters are available in the Metrics tab:

  • Progression: All configured progressions in Continuum
  • Dashboard: Available dashboards are "flow" and "risk"
  • Package: All packages associated with the selected progression will show here
  • Version: All available versions for the given package will show here

The following tiles are available under each of the dashboards:

Flow

  • Current Workitem Count by Phase: Shows the number of workitems currently in each phase. Broken down by workitem type (story, defect, etc).
  • Workitem Lead Time: The amount of time it takes for a workitem to make it across the progression end-to-end. Shows average for all workitem on the progression, mid-point value (median), fastest (min) and slowest (max). Calculated from the first commit event to delivery.
  • Efficiency by Phase: The relation between "touch-time" (processing time) and "wait-time" (idle time) for each phase. Calculated by dividing touch-time over cycle-time. Less "wait-time" will translate into higher efficiency.
  • Efficiency: The relation between "touch-time" (processing time) and "wait-time" (idle time) for the entire progression. Calculated by dividing touch-time over lead-time. Less "wait-time" will translate into higher efficiency.

Risk

  • Change Arrivals: Illustrates the age of change (commits) in relation to delivery time to the "code complete" phase. An even distribution translates to steady and consistent delivery. An uneven distribution with a high number of spikes translates into large, uneven pushes. Large deliveries close to the "code complete" phase may indicate risk.
  • Rogue Commit Percentage: The number of commits that are correctly associated to a workitem (managed commits) vs. the number of commits that are NOT associated to a workitem (rogue commits). Rogue commits translate to untracked/lost value in the progression.
  • Risk Averages
    • Risk Index: Scale from 0 - 100 indicating risk for the given version (where 0=least risk, 100=most risk). Calculated with a formula based on the individual file level frequency of change, defect to story ratio, and complexity rank.
    • High Risk Revisions: Number of revisions with a Risk Index greater than 5 for the particular version.
    • High Risk Files: Number of files deemed to be "high risk", based on the number of defects associated with the files in version control.
    • Risky Files/Total Changed: Number of risky files in the version vs. number of files that were changed/updated.
    • Complexity Rank: Normalized complexity value across all files across a version (only available when SonarQube integration is enabled).
  • Value Goal Averages
    • Value Ratio: Ratio of stories to defects for the given version
    • New Value: Percentage of stories for the given version
    • Maintenance: Percentage of defects for the given version
    • Improving: Total number of stories for the given version
    • Maintaining: Total number of defects for the given version
  • Was this article helpful?