Skip to main content

Metrics

Q247 measures development work from data the team produces anyway: commits, tickets and documentation pages. This part of the documentation explains where every number visible on the Dashboards comes from and how to read it.

Calories, Increments and Lines as the foundation​

Calories, Increments and Lines are the three base units the remaining metrics are calculated from.

Calories Type is a selector present on every dashboard. It switches which activity the metrics are calculated from, so the same card can show different values depending on its setting. It has three options:

  • Total: commits, pushes, Jira tickets and Confluence pages together.
  • Coding: only commits and pushes to a repository.
  • Documentation: only Jira tickets and Confluence pages.

Metric groups​

GroupWhat it describesLevel
Calories, Increments and Linesthe amount of work doneparticipant, project, team
Activity periodwhen activity started and endedparticipant
Work Dynamics Indexesregularity and rhythm of workparticipant, aggregated upwards
Gradea participant's position relative to the othersparticipant
Retentionhow long the code written survivesparticipant, project, team
Team Capacityhow many people actually worked in the periodproject, team
Flow Metricshow long a ticket takes to pass through the processproject only
Workloadthe distribution of work over timeparticipant, team
Worklogstime reported in Tempoparticipant

Required integrations​

Most metrics are calculated from code repositories, so a configured connector is enough for them.

Two groups require additional integrations. Flow Metrics need Jira, because they are calculated from the history of ticket status changes. Worklogs need Tempo.

Rules common to all metrics​

Level of measurement. Metrics are calculated for an individual participant, and the values at project and team level come from aggregating those same values. The same participant therefore has one value of each metric in a given period, no matter which view you look at it from.

Period. Every number refers to the period selected with the selector at the top of the page. When comparing two periods of different length, check whether the metric in question is normalized per week.

Exclusions. Part of the work can be left out of the calculations, and two different people do that. Individual commits are excluded by a project manager or a team manager, directly from the Project, Team or Participant view, which Commit exclusion describes. Rules that apply to the whole organization, that is file patterns, the automatic skipping of cherry-picks, reverts and rebases, and the increment visibility threshold, are set by an administrator in Configuration. The effect of both is visible across all metrics at once.

An aggregate value and the participant table

The same team result can come from an even contribution by several people or from the work of one. Only the level below settles that, in the participant table of the project or team in question.

Subpages​

See also​