📘 Waydev Metrics

Impact - When calculating Impact, each commit is scored on new work, legacy refactoring, helping others, and churn. We also consider the number of modified files and change points. The score relates to team factors like active contributors and average active days.

Efficiency - The percentage of productive code, independent of the amount of code written. The higher the efficiency rate, the longer the code provides business value.

Active Days - The number of days a contributor was active (code commited, PR activity)

New Work (%) - New code added to the code base (without replacing old code)

Refactor (%) - Code that has been updated or rewritten after 21 days (this value is adjustable on the Settings page)

Help (%) - Code that has been updated by another contributor, not the one who initially wrote it.

Churn (%) - Code that has been rewritten or deleted in the first 21 days (this value is adjustable on the Settings page)

New Work (LoC) - New code added to the code base (without replacing old code)

Refactor (LoC - Code that has been updated or rewritten after 21 days (this value is adjustable on the Settings page)

Help (LoC) - Code that has been updated by another contributor, not the one who initially wrote it.

Churn (LoC) - Code that has been rewritten or deleted in the first 21 days (this value is adjustable on the Settings page)

Technical Debt - It is the amount of refactoring code done in the selected time frame.

Productive Throughput - Productive Throughput is the proportion of code without churn.

Throughput - Throughput represents the total amount of code of new work, churn code, help others and refactored code.

Low Risk Commits - The number of low-risk commits.
*Risk is a measure of how likely a commit is to cause problems. It is calculated based on the size of the commit, how the changes are spread across the code base, and how serious the changes are.

Medium Risk Commits - The number of medium-risk commits.
*Risk is a measure of how likely a commit is to cause problems. It is calculated based on the size of the commit, how the changes are spread across the code base, and how serious the changes are.

High-Risk Commits - The number of high-risk commits.
*Risk is a measure of how likely a commit is to cause problems. It is calculated based on the size of the commit, how the changes are spread across the code base, and how serious the changes are.

Code Impact - The Impact of work done related to code. (work size, percentage of the work edited to old code, number of edit locations, number of files affected, the severity of changes, and how this change compares to others)

Pull Requests Impact - The impact of work done related to Pull Requests.

Code Active Days - The average days per month a team member makes at least one commit.

Commits - It represents the amount of commits done by the contributor.

Commits/Day (commits) - Commits/Active Day is the ratio between total number of commits and total active days.

Pull Requests Active Days - The average days per month a team member makes at least one Pull Request.

Total Pull Requests - The total number of Pull Requests from the selected period.

Total Merged Pull Requests - Pull Requests Merged represents the PRs that are merged (no matter if they were reviewed or not).

Total Pull Requests Merged Without Review - Represents the Pull Requests that are merged without review.

Total Closed Pull Requests- Represents the Pull Requests that are closed.

Total PR Comments - Represents the overall count of comments made on Pull Requests.

Total Open Pull Requests - Total Open Pull Requests represents the total of pull requests that are open.

Total Pull Requests Commented - Represents the total number of Pull Requests on which at least one comment has been made.

Follow-On Commits - Follow-On Commits indicate how many additional commits Pull Requests require to be resolved from the moment they were created.

Knowledge Sharing Index - The Sharing index shows if you have enough reviewers to handle all Pull Request submissions. It is calculated as the ratio of unique PR reviewers to unique PR submitters.

Reviewer Comments / PR - Represents the number of comments made by reviewers on each Pull Request.

Unreviewed Pull Requests - Represents the percentage of PRs submitted that had no comments.

Iterated Pull Requests - the total number of pull requests with a follow-on commit divided by the total number of pull requests.

Average PR Iteration Time - the difference in time between the timestamp of the final commit on the pull request and the timestamp of the first non-excluded, non-submitter comment. If a pull request has no follow-on commits after a non-submitter comment, the PR iteration time for the pull request is 0. The PR iteration time for an individual, team, or organization is calculated as the sum of the PR iteration times for all pull requests created by them, divided by the total number of pull requests, rounded to the nearest tenth of an hour.

Total Pull Requests Reviewed - Indicates the number of Pull Requests that have been reviewed by one or more reviewers.

Total Pull Requests Without Reviews- Represents the number of Pull Requests that have not undergone any review by designated reviewers.

Total Pull Requests Without Comments - Refers to the count of Pull Requests that have been created and merged without any comments or feedback from reviewers.

Total Pull Requests Merged Without Rebase - Represents the number of Pull Requests that have been merged into the target branch without undergoing the rebase operation.

Total PR Reviews - Refers to the overall count of reviews performed on Pull Requests

Average comments/PR - The total number of comments (from anybody except assigned reviewers) divided by the total number of Pull Requests (opened, merged, and closed)

Average time to merge from review - Measures the average duration it takes for a Pull Request (PR) to be merged from the moment of its first review.

Average time to merge from create - Represents the average duration it takes for a Pull Request (PR) to be merged from the moment of its creation.

Average time to merge from comment - Refers to the average duration it takes for a Pull Request (PR) to be merged from the moment of the first comment made on the PR.

Average time to first comment - Represents the average duration it takes for a Pull Request (PR) to receive the first comment from reviewers or collaborators.

Average time from merge to deploy - Refers to the average duration it takes for a Pull Request (PR) to be merged and subsequently deployed to a production environment.

Average time to first review - The average time it takes for the first review to be made on a Pull Request.

Average time to issue PR- Represents the average duration it takes for a Pull Request (PR) to be issued after the first commit is made.

Average time to merge from first commit - Represents the average duration it takes for a Pull Request (PR) to be merged after the first commit is made.

Cycle Time - Cycle Time is one of the best measures of an engineering organization’s velocity. It measures the elapsed time from the first commit made to production release.

Lead Time For Changes - Measures the amount of time it takes for code to get into production from the first commit made.

Deployment Frequency - Measures how often code is deployed into production, including bug fixes, capability improvements, and new features.

Total Deployments - Total number of deployments.

Change Failure Rate - Measures the percentage of deploys that cause a failure in production.

Mean Time To Recovery - Measures the amount of time it takes to recover from a failure in production.

Failed PRs - Refers to the cumulative count of Pull Requests (PRs) that have encountered issues or failures during the review and merging process.

PR Failure Rate - The PR Failure Rate indicates the percentage of Pull Requests declined or closed to total Pull Requests, excluding Pull Requests in progress.

Collaborative Throughput - Collaborative Throughput represents the total number of lines that are affected in commits that the contributor participated in but is not the main author. The way this is calculated can be adjusted in the Settings page.

Collaborative Commits - Commits that have collaborators.

tt100 - tt100 represents the time it takes for a contributor to create 100 productive lines of code (code without churn).

Work Type - Work Type represents the highest types of work an engineer is focused on (New Work, Legacy Refactor, Help Others, and Churn).

Pull Request Size - The number of lines of code that were modified, added, or deleted.

Traceability - The percentage of commits that are linked to at least one ticket.

Traceable Commits - The number of commits that are linked to at least one ticket.

Code active weeks - The average number of weeks a team member makes at least one commit.

Weekly coding days - The average days per week a team member makes at least one commit.