Waydev Metrics

Code Stats

Metric	Definition
Active Days	Number of days with any activity from contributors.
Commits	Number of code commits made by contributors.
Collaborative Commits	Number of commits to a repository involving more than one contributor.
Code Active Days	Number of days with contributor code commits.
Commits/Day (commits)	Number of code commits made by contributors per days with contributor code commits.
Total Pull Requests	The total number of Pull Requests.
Throughput (LoC)	Total lines of new, churn, help and refactored code.
Productive Throughput (LoC)	Total lines of new, help and refactored code.
Collaborative Throughput	Total lines affected in code commits in which contributor participated in but is not the main author.
Low Risk Commits	Risk is a measure of how likely a commit is to cause problems (code quality/stability). 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	Risk is a measure of how likely a commit is to cause problems (code quality/stability). 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	Risk is a measure of how likely a commit is to cause problems (code quality/stability). 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.
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.
Weekly Coding Days	Average number of days within a given week that an individual or team dedicates to engineering work like writing code, reviewing other's work, discuss architecture and push commits.
Technical Debt	Amount of refactoring code commited. Represents the volume of code modifications aimed at improving internal structure, readability, or maintainability, without altering the external behavior of the software.
New Work (LoC)	Total lines of code added to the code base (without replacing old code).
New Work (%)	Percentage of new lines of code reported to total (new, churn, help and refactored).
Refactor (LoC)	Total lines of code restructured to improve readability, design, or reduce technical debt.
Refactor (%)	Percentage of refactored lines of code reported to total (new, churn, help and refactored).
Help (LoC)	Total number of code lines authored with the intent to support or enable other contributors.
Help (%)	Percentage of help lines of code reported to total (new, churn, help and refactored).
Churn (LoC)	Total number of lines of code that were added and subsequently removed or modified within a short time frame.
Churn (%)	Percentage of churn lines of code reported to total (new, churn, help and refactored).
Commits Score	Sum of code commits score. The commit score provides a single metric that rewards meaningful contributions, penalises risky changes, helps identify high-quality vs. problematic commits, balances quantity (impact) with quality (risk).
tt100	TT100 represents the time it takes for a contributor to create 100 productive lines of code (without churn).
Work Type	Represents the highest types of work an engineer is focused on (New Work, Legacy Refactor, Help Others, and Churn).

Pull Request Stats

Metric	Definition
Merged PRs	Total Merged Pull Requests is a count metric that measures the number of pull requests that were successfully merged into the main codebase in a given time period.
Total Pull Requests Merged Without Review	Total Pull Requests Merged Without Review is a count metric that measures the number of pull requests that were merged without undergoing the required code review process.
Total Closed Pull Requests	Total Closed Pull Requests is a count metric that measures the number of pull requests that were closed without being merged in the project management system.
Total Open Pull Requests	Total Open Pull Requests is a count metric that measures the number of pull requests that are currently open and awaiting review, approval, or completion in the project management system.
Total Failed Pull Requests	Tracks the total number of pull requests that failed during the specified time period.
Total Pull Requests Commented	Tracks the total number of pull requests that received comments during the specified time period.
Reviews received (reviews)	Tracks the total number of pull request reviews performed during the specified time period.
Total Pull Requests Reviewed	The total number of pull requests that received at least one review during the specified time period.
Total Pull Requests Without Reviews	The number of pull requests that were merged or closed without receiving any code reviews from other team members.
Total Pull Requests Without Comments	This metric counts how many pull requests (code changes) received no comments or feedback from reviewers during the development process.
Total Pull Requests Merged Without Rebase	This metric counts how many pull requests were merged into the main codebase without first being cleaned up or reorganized to match the current state of the main code.
Comments received (comments)	The total number of comments left on pull requests during a specific time period.
PRs-Merged-and-Commented	The number of pull requests that were both successfully merged into the main codebase AND received comments during the review process.
PR Failure Rate (%)	The percentage of pull requests that failed during a specific time period.
Pull Requests Active Days	The number of unique days during a time period when pull requests were actively being worked on (created, reviewed, or merged).
Lead Time for Changes	The total time (in seconds) it takes for a code change to go from the first commit to being successfully deployed to production. It's like measuring how long it takes for a product idea to go from concept to being available to customers.
Follow-On Commits	The total number of additional commits that were made to fix issues or make improvements after a pull request was initially created.
Total Thoroughly Reviewed PRs	The total number of pull requests that received thorough, meaningful reviews rather than just quick approvals or rubber-stamp reviews.
Total Rubber Stamped PRs	The total number of pull requests that were approved with minimal or no meaningful review - essentially "rubber stamped" through the approval process.
Total Iterated PRs	The total number of pull requests that went through multiple rounds of review and revision before being finally merged.
Total Reviewer Comments	The total number of comments made by reviewers across all pull requests during the specified time period.
Pull Requests Impact	A composite score that evaluates how impactful pull request activity has been during a specific time period, considering factors like the number of active days, number of contributors, and the overall pull request score.
Impact	A composite score that represents the overall effectiveness and productivity of development work across all activities (code commits, pull requests, and other development tasks) during a specific time period.
Avg. to first comment	The average amount of time it takes for someone to leave the first comment on a pull request after it's created.
Avg. to first review	The average amount of time it takes for a pull request to receive its first review after being created.
Avg. to merge from create	The average amount of time it takes for a pull request to go from creation to successful merge across all pull requests in a given time period.
Avg. to merge from first commit	The average amount of time it takes for a pull request to be merged, starting from when the first code change (commit) was made, rather than when the pull request was officially created.
Avg. to merge from first comment	The average amount of time it takes for a pull request to be merged after receiving its first comment from a reviewer.
Avg. to merge from first review	The average amount of time (in seconds) that pull requests take from when they receive their first review until they are successfully merged into the main codebase.
Avg. to issue PR	The average amount of time it takes for developers to create a pull request after they make their first code change (commit) in a feature branch.
Avg. from merge to deploy	The average amount of time it takes for code changes to go from being merged into the main codebase to being deployed to production (where users can actually use the new features).
Avg. comments/PR	The average number of comments left on each pull request during the review process.
Knowledge Sharing Index	A score that indicates how well knowledge is being shared across the development team through code reviews. It measures the diversity and distribution of review participation.
Reviewer Comments per PR	The average number of comments that reviewers leave on each pull request during the code review process.
Thoroughly Reviewed PRs %	The percentage of pull requests that received thorough, high-quality reviews rather than just quick approvals or rubber-stamp reviews.
Rubber Stamped PRs %	The percentage of pull requests that were "rubber stamped" - meaning they received very quick, superficial reviews that likely didn't provide meaningful feedback or catch potential issues.
Unreviewed PRs (%)	The percentage of pull requests that were merged into the main codebase without receiving any code reviews from other team members.
Iterated PRs	The percentage of pull requests that required multiple rounds of changes and reviews before being approved and merged.
Avg. PR Iteration Time	The average amount of time (in seconds) that pull requests spend in "iteration cycles" - the back-and-forth process between developers and reviewers when changes are requested and implemented.
Avg. PR Size (LoC)	The average number of lines of code changed across all pull requests in a given time period.

DORA Metrics

Metric	Definition
Total Deployments	Total Deployments is a count metric that measures the number of successful releases/deployments in a given time period across selected repositories.
Deployment Frequency (per day)	Deployment Frequency is a key DORA metric that measures how often code is deployed to production (or another target environment) within a given time period.
Failed Deployments	Failed Deployments is a count metric that measures the number of deployments that resulted in incidents or failures in a given time period.
Change Failure Rate	Change Failure Rate is a percentage-based metric that measures the proportion of deployments that result in failures or incidents in a given time period.
Number of Incidents	Number of Incidents is a count metric that measures the total number of incidents that occurred in a given time period across selected repositories.
Mean Time To Recovery	Mean Time to Recovery (MTTR) is an average metric that measures the average time it takes to recover from incidents in a given time period.

Ticket Stats

Metric	Definition
Touched Tickets	Touched Tickets is a count metric that measures the total number of tickets that were touched or interacted with in a given time period across selected project management (PM) projects.
Created Tickets	This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the Created stage of the development process.
Tickets in ToDo	This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the ToDo stage of the development process.
Tickets in Development	This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the Development stage of the development process.
Tickets in QA	This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the QA stage of the development process.
Resolved Tickets	This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the Resolved stage of the development process.
Active Tickets	This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the Active stage of the development process.
Bug Tickets in ToDo	This metric tracks bug tickets based on their state/category in the project management workflow. The metric represents bug tickets in the ToDo stage of the development process.
Bug Tickets in Development	This metric tracks bug tickets based on their state/category in the project management workflow. The metric represents bug tickets in the Development stage of the development process.
Bug Tickets in QA	This metric tracks bug tickets based on their state/category in the project management workflow. The metric represents bug tickets in the QA stage of the development process.
Resolved Bug Tickets	This metric tracks bug tickets based on their state/category in the project management workflow. The metric represents bug tickets in the Resolved stage of the development process.
Active Bug Tickets	This metric tracks bug tickets based on their state/category in the project management workflow. The metric represents bug tickets in the Active stage of the development process.
Assigned tickets	This metric tracks tickets assigned to a specific developer in the project management system.
Unassigned Tickets	This metric tracks tickets that remain unassigned in the project management system.
Planned Tickets	This metrics tracks tickets were planned in advance (part of sprint/iteration planning).
Unplanned Tickets	This metric tracks unplanned tickets(emergency work, bugs, or ad-hoc requests).
Tracked Tickets	These metric distinguishes between tickets that are explicitly tracked in the project management system and those that are not tracked (work done outside the formal tracking system).
Untracked Tickets	This metric distinguishes between tickets that are explicitly tracked in the project management system and those that are not tracked (work done outside the formal tracking system).
Estimated Tickets	This metric tracks tickets that have been assigned story points (estimated).
Unestimated Tickets	This metric tracks tickets that lack story points (unestimated) in the project management system.
Epicless Tickets	Epicless Tickets is a count metric that measures the number of tickets that are not associated with any epic in the project management system.
Unlinked Tickets	Unlinked Tickets is a count metric that measures the number of tickets that have no associated Git activity (commits or pull requests) in the project management system.
Stalled Tickets	Stalled Tickets is a count metric that measures the number of tickets that have been inactive for an extended period and are considered "stalled" in the project management system.
Stuck Tickets	Stuck Tickets is a count metric that measures the number of tickets that are blocked or impeded from progressing due to specific issues or dependencies in the project management system.
Subtask Tickets	Subtask Tickets is a count metric that measures the number of subtasks associated with tickets in the project management system.

Story Points Stats

Metric	Definition
Story Points Touched	Story Points Total is a cumulative metric that measures the total sum of all story points across all estimated tickets in the project management system.
Story Points Created	This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Created stage of the development process.
Story Points in ToDo	This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the ToDo stage of the development process.
Story Points in Development	This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Development stage of the process.
Story Points in QA	This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the QA stage of the development process.
Story Points Resolved	This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Resolved stage of the development process.
Story Points Bug Created	This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the Created stage of the development process.
Story Points Bug in ToDo	This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the ToDo stage of the development process.
Story Points Bug in Development	This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the Development stage of the process.
Story Points Bug in QA	This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the QA stage of the development process.
Story Points Bug Resolved	This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the Resolved stage of the development process.
Story Points Active	This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Active stage of the development process.
Story Points Bug Active	This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the Active stage of the development process.
Planned Story Points	These metrics track story points based tickets which were planned in advance (sprint planning).
Unplanned Story Points	These metrics track story points that were not planned in advance (emergency work, ad-hoc requests) in the project management system.
Tracked Story Points	Story Points Tracked is a cumulative metric that measures the total sum of story points for tickets that are explicitly tracked in the project management system, regardless of whether they were planned or unplanned.
Story Points per Tracked Tickets	Story Points Per Tracked Tickets is an average metric that measures the average number of story points per tracked ticket in the project management system.

Total Time stats

Metric	Definition
Total Time: PRs Iterations	The total amount of time (in seconds) that all pull requests spent in "iteration cycles" - the back-and-forth process between developers and reviewers when changes are requested, made, and re-reviewed.
Total Time: PRs Create → Merge	The total amount of time (in seconds) that all pull requests took from when they were first created until they were successfully merged into the main codebase.
Total Time: PRs First Review → Merge	The total amount of time (in seconds) that all pull requests took from when they received their first review until they were successfully merged into the main codebase.
Total Time: PRs Create → Review	The total amount of time (in seconds) that all pull requests waited from when they were first submitted until someone provided the first review or feedback.
Total Time: PRs Create → Comment	The total amount of time (in seconds) that all pull requests took from when they were first created until someone left the very first comment on them.
Total Time: PRs Merge → Deploy	The total amount of time (in seconds) that all pull requests took from when they were successfully merged into the main codebase until they were deployed to production (live environment where users can access the changes).
Total Time: PRs Comment → Merge	The total amount of time (in seconds) that all pull requests took from when the first comment was made on them until they were successfully merged into the main codebase.
Total Time: PRs Commit → Merge	The total amount of time (in seconds) that all pull requests took from when the first code change was made until the pull request was successfully merged into the main codebase.
Total Time: Commit → PRs Create	The total amount of time (in seconds) that developers spent working on code changes before creating pull requests. It measures the time from when a developer first started making changes (first commit) until they felt the changes were ready for review (pull request creation).
Total Time: PRs Iterations	The total amount of time (in seconds) that all pull requests spent in "iteration cycles" - the back-and-forth process between developers and reviewers when changes are requested, made, and re-reviewed.
Total Time: Incidents → Recovery	Total Time to Recovery is a cumulative metric that measures the total time spent recovering from incidents across all incidents in a given time period.