Project metrics
Process metrics express, in quantitative form, how far project goals are met, and they visualize problems that need to be solved. Metrics are closely tied to the process and the management approach. Different processes can have their own specific metrics.
The list of metrics is available in the "Metrics" module:
| System metric | Description |
|---|---|
| Project budget | This metric describes the current project budget. It is the sum of all expense and income budget lines for the project. |
| Average team velocity | In Agile metrics mode, when iterations or sprints are used, average velocity is calculated from the actual velocity of the last 5 completed iterations. Otherwise it is calculated from the average estimate of completed issues and stories per week. If estimation is not used, it is calculated from the average number of completed issues or stories per week. |
| Requirements covered by test documentation |
The percentage of requirements whose type implies testing and that have related test scenarios. This indicator shows how far project requirements are covered by test documentation. |
| Outdated... | The number of project artifact sections marked as outdated, that is, no longer consistent with the source requirements. |
A metric can be added to the dashboard. To do this, use the menu item:
Custom metrics
To create custom metrics, use the corresponding green button.
- A COUNT/AVG metric calculates a count or an average for a given search query on some entity. For example, the number of unfixed defects, and so on.
- A % metric calculates a ratio and expresses it as a percentage. For example, for some entity, the percentage of unfinished records relative to the total number of records. It is configured by setting search queries for the numerator and the denominator.
Thresholds
Use threshold limits on metrics to visualize problems related to the metric value. Exceeding the "Warning" threshold turns the metric indicator background orange. Exceeding the "Danger" threshold turns the background red.
Thresholds implement a management "traffic light" that quickly identifies problem projects so you can start correcting the deviations found.
Showing metrics on the dashboard lets you react quickly to deviations that appear in the project
How metrics change
For each metric, the value is stored for every day of the project. The "Metric trend" chart shows how the metric value changed over time.
For example, you can build a report "Ratio of created requests to resolved requests". Create two metrics:
- "Number of issues created" — Entity: Issue, Function: COUNT, Query: FinishDate = ""
- "Number of issues resolved" — Entity: Issue, Function: COUNT, Query: FinishDate != ""
Then open the "Metric trend" chart and, in the filter settings, select the two metrics you created. Save the report under a name that is convenient for you.
Personal metrics
Personal metrics are collected on a dashboard available from the "Indicators" menu in the user profile:
To configure personal metrics for participants of a specific project, go to the "Participants" module, open the "Artifact dashboard" panel on the right, and click "Add":
