The following article explains all the metrics you can find in our product and how to use them to potentiate your engineering teams.
*Pull Request and Merge Request mean the same thing (Pull Requests are used in GitHub and Bitbucket and Merge Requests in Gitlab). In this document, we will use the term Pull Request or PR to refer to both concepts.
Table of Contents:
Project Management / Agile Metrics
Sprints Metrics
DORA Metrics
Calendar & Meets Metrics
Coding Details Metrics
Commits
Definition: Number of commits opened in a time range.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Teams > Coding Details
• Contributor > Contributor List
• Contributor > Summary
• Contributor > Coding Details
Additions
Definition: Number of lines of code added in a time range.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Contributor > Contributor List
• Contributor > Coding Details
Deletions
Definition: Number of lines of code deleted in a time range.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Contributor > Contributor List
• Contributor > Coding Details
Pull Requests Opened
Definition: Number of Pull Requests opened in a time range.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Teams > Coding Details
• Contributor > Contributor List
• Contributor > Summary
• Contributor > Coding Details
Pull Requests Merged
Definition: Number of Pull Requests that were merged to the target branch in a time range.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Teams > Teams List
• Teams > Summary
• Teams > Coding Details
• Contributor > Contributor List
• Contributor > Summary
• Contributor > Coding Details
Pull Requests Merged By
Definition: Pull Requests where the contributor clicked on the “Merge” button in a time range.
Notes:
• Only Pull Requests where the person that merged the PR is different than the one that opened the PR are counted.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Contributor > Contributor List
• Contributor > Summary
• Contributor > Coding Details
Pull Requests Reviewed
Definition: Number of Pull Requests where the team or contributor left a Review Comment in a time range.
Notes:
• A PR Review Comment is a comment left on a specific line or lines of code in the PR.
• Only Comments left by people different than the one that opened the PR are counted.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Teams > Teams List
• Teams > Summary
• Teams > Coding Details
• Contributor > Contributor List
• Contributor > Summary
• Contributor > Coding Details
Pull Requests Review Comments
Definition: Total Number of Review Comments left in Pull Requests in a time range.
Notes:
• A PR Review Comment is a comment left on a specific line or lines of code in the PR.
• Only Comments left by people different than the one that opened the PR are counted.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Teams > Summary
• Contributor > Contributor List
• Contributor > Summary
• Contributor > Coding Details
Self-Merged PRs
Definition: Number of Pull Requests where the creator was the same as the one that merged the PR.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Teams > Coding Details
PRs Merged to Prod
Definition: Number of Pull Requests merged where the target branch is Prod, Production, Main, or Master.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Teams > Summary
• Teams > Coding Details
PRs Merged to Prod
Definition: Number of Pull Requests merged where the target branch is Prod, Production, Main, or Master.
Data Source: Github, Gitlab, or Bitbucket
Can be found in:
• Teams > Summary
• Teams > Coding Details
Project Management / Agile Metrics
Epic Start Date
Definition: First timestamp when a Jira Issue or Notion Task that is part of the Epic was moved to an “In Progress” status or “Done” status.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Epics Summary
Epic Resolution Date
Definition: Timestamp when an Epic was moved to a “Done” status.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Epics Summary
• Initiatives > Epic Details
Epic Progress
Definition: Number of completed Tasks divided by the total number of Tasks related to the Epic, displayed as a percentage. Can be calculated based on Story Points or Number of Tasks.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Epics Summary
• Initiatives > Epic Details
Epic Allocation (%)
Definition: From all the Story Points processed related to Epics in a time range, the percentage that was dedicated to a specific Epic.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Summary
Tasks Created
Definition: Number of Jira Issues or Notion Tasks created by the Team or Contributor in a time range.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Task Details
• Contributor > Summary
• Contributor > Task Details
Tasks / Story Points Completed
Definition: Number of Story Points / Jira Issues or Notion Tasks completed in a time range, Epic, Sprint, or Project.
Notes: Tasks closed with a status of “Dismiss”, “Canceled”, or “Won’t Do” are not counted.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Teams List
• Teams > Summary
• Teams > Task Details
• Teams > Projects Summary
• Teams > Sprints Summary
• Teams > Epics Summary
• Contributor > Contributor List
• Contributor > Summary
• Contributor > Task Details
• Contributor > Sprint Details
• Initiatives > Sprint Details
• Initiatives > Project Details
• Initiatives > Epic Details
Tasks Canceled
Definition: Number of Jira Issues or Notion Tasks that were closed with a status of “Canceled”, “Won’t Do”, or “Dismiss”.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Task Details
SD Tickets Processed
Definition: Jira Service Desk Tickets Closed or Completed in a time range.
Data Source: Atlassian Jira Service Desk
Can be found in:
• Teams > Teams List
• Teams > Summary
• Teams > Task Details
• Contributor > Contributor List
• Contributor > Summary
• Contributor > Task Details
SD Tickets Created
Definition: Jira Service Desk Tickets Created in a time range.
Data Source: Atlassian Jira Service Desk
Can be found in:
• Teams > Task Details
• Contributor > Task Details
Task Lead Time
Definition: Time difference between Task Creation and Task Completion.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Task Details
• Contributor > Task Details
• Initiatives > Project Details
• Initiatives > Sprint Details
• Initiatives > Epic Details
Task Cycle Time
Definition: Time difference between Task Start Date (the moment a Task was moved to an “In Progress” Status) and Task Completion.
Notes: If the Task was moved from “To Do” to “Done”, the Cycle Time is not calculated.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Task Details
• Contributor > Task Details
• Initiatives > Project Details
• Initiatives > Sprint Details
• Initiatives > Epic Details
Sprints Metrics
Sprint Start Date
Definition: Date defined as the start date of a sprint.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Sprints Summary
• Initiatives > Sprint Details
Sprint End Date
Definition: Date defined as the end of the sprint. This is defined when a sprint is created.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Sprints Summary
• Initiatives > Sprint Details
Sprint Completed Date
Definition: Actual date when the sprint is completed or closed. The customer has to mark the sprint as completed for this field to be populated, as long as this field is empty, the sprint is considered open or running even though the end date already occurred.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Sprints Summary
• Initiatives > Sprint Details
Sprint Total Scope
Definition: Indicates the total number of Jira Issues or Notion Tasks that were added at any point in time to a sprint (this metric can also be displayed based on story points).
Notes: This metric considers all the tasks that were part of a sprint, even if they were later moved to a different sprint or backlog.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Sprints Summary
• Initiatives > Sprint Details
Sprint Initial Scope
Definition: Indicates the total number of Jira Issues or Notion Tasks that were added to a sprint before the sprint started or in the first two days of the sprint (this metric can also be displayed based on story points).
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Sprints Summary
Completion Rate
Definition: Number of completed Jira Issues or Notion Tasks in a sprint divided by the total scope of a sprint, displayed as a percentage (this metric can also be displayed based on story points).
Notes: Tasks closed with a status of “Dismiss”, “Canceled”, or “Won’t Do” are not counted as completed tasks; however, they do count as part of the Sprint Total Scope.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Teams List
• Teams > Summary
• Teams > Sprints Summary
• Contributor > Sprint Details
• Initiatives > Sprint Details
Planned Work Completion Rate
Definition: Percentage of completed Jira Issues or Notion Tasks only considering the Sprint Initial Scope, meaning only considering the Tasks that were added to the sprint in the first two days (this metric can also be displayed based on story points).
Notes: Tasks closed with a status of “Dismiss”, “Canceled”, or “Won’t Do” are not counted as completed tasks; however, they do count as part of the Sprint Scope.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Sprints Summary
• Contributor > Sprint Details
• Initiatives > Sprint Details
Unplanned Work
Definition: Percentage of Jira Issues or Notion Tasks that were added to the sprint three or more days after the Sprint Start Date (this metric can also be displayed based on story points).
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Teams List
• Teams > Summary
• Teams > Sprints Summary
• Contributor > Sprint Details
• Initiatives > Sprint Details
Unplanned Work Completion Rate
Definition: Considering only the Unplanned Work, the percentage of Jira Issues or Notion Tasks that were completed in the sprint (this metric can also be displayed based on story points).
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Teams List
• Teams > Summary
• Teams > Sprints Summary
• Contributor > Sprint Details
• Initiatives > Sprint Details
Work Carried Over
Definition: This metric shows the percentage of work (Tasks or Story Points) that were carried over from a previous sprint to the selected sprint.
Data Source: Atlassian Jira, Notion
Can be found in:
• Teams > Sprints Summary
• Contributor > Sprint Details
DORA Metrics
PR Cycle Time
Definition: Time it takes from the first commit associated with a Pull Request until the Pull Request is merged to the production branch.
Data Source: Github, Gitlab, Bitbucket
Can be found in:
• Teams > DORA
PR Coding Time
Definition: The coding time is part of the Pull Request Cycle time and measures the time it takes from the first commit associated with the pull request to the time the pull request is created.
Data Source: Github, Gitlab, Bitbucket
Can be found in:
• Teams > Coding Details
PR Pickup Time
Definition: The pickup time is part of the Pull Request Cycle time and measures the time it takes from the pull request creation to the first interaction (a comment or review comment) from the pull request reviewer.
Data Source: Github, Gitlab, Bitbucket
Can be found in:
• Teams > Coding Details
PR Review Time
Definition: The Review time is part of the Pull Request Cycle time and measures the time it takes from the first pull request interaction to the pull request merge.
Data Source: Github, Gitlab, Bitbucket
Can be found in:
• Teams > Coding Details
Deploys per Day
Definition: Deploys per day or deploy frequency provides the number of Pull Requests that were merged to the production branch in a day.
Data Source: Github, Gitlab, Bitbucket
Can be found in:
• Teams > DORA
Change Failure Rate (CFR)
Definition: Percentage of production deployments that resulted in incidents or errors in a selected period of time.
Data Source: Github, Gitlab, Bitbucket
Can be found in:
• Teams > DORA
Mean Time to Restore (MTTR)
Definition: This metric indicates the time it took to restore a service from an incident.
Data Source: Github, Gitlab, Bitbucket
Can be found in:
• Teams > DORA
Calendar & Meets Metrics
Scheduled Meet Time
Definition: Time scheduled for meets of two or more people in a week, based on calendar data.
Data Source: Google Calendar
Can be found in:
• Teams > Teams List
• Teams > Summary
• Contributor > Contributors List
• Contributor > Summary
• Contributors > Meeting Details
Actual Meet Time (Coming Soon)
Definition: Actual time spent in meets in a week.
Data Source: Google Meet
Scheduled One-on-one Time
Definition: Time scheduled for meets of two people in a week, based on calendar data.
Data Source: Google Calendar
Can be found in:
• Contributor > Summary
• Contributors > Meeting Details
Fragmented Time
Definition: Sum of time slots of 30 minutes or less between meetings. Usually, this tiny fragments represent unproductive time for software developers, since it is a very short period of time to accomplish something meaningful. Organizations should aim to have this metric close to zero.
Data Source: Google Meet
Can be found in:
• Contributors > Meeting Details
Deep Work Time
Definition: Sum of time slots of 2 hours or more between meetings. It is important for software developer to have plenty of deep work time per week.
Data Source: Google Meet
Can be found in:
• Contributors > Meeting Details
Out of Office Time
Definition: Sum of time slots of 2 or more hours marked as "Out of Office". By measuring this indicator, Kindor can decide when to trigger inactivity alerts. For example, if a contributor was out of office for one week, inactivity warnings won't be triggered during that time period.
Data Source: Google Calendar
Can be found in:
• Contributors > Meeting Details
Attendance Rate
Definition: From all the Google Calendar Events accepted, the percentage the contributor attended (based on Google Meet Data). A 100% attendance rate means that the contributor connected to all Google Calendar events that were accepted. This metric could not represent the reality if the team is attending the meets in person and not through Google Meet.
Data Source: Google Calendar & Google Meet
Can be found in:
• Contributors > Meeting Details
Punctuality Rate
Definition: From all the Google Calendar Events accepted and attended, the percentage to which the contributor connected within 5 minutes of its start time.
Data Source: Google Calendar & Google Meet
Can be found in:
• Contributors > Meeting Details
Meetings Efficiency Rate
Definition: From all the Google Meets attended, the percentage that ended on time or within a window of 5 minutes of tolerance.
Data Source: Google Calendar & Google Meet
Can be found in:
• Contributors > Meeting Details
Organized Meetings
Definition: From all the meetings a contributor has scheduled in a time frame, the percentage of meetings that the contributor organized.
Data Source: Google Calendar
Can be found in:
• Contributors > Meeting Details
Comments