Team Progress

Track the progress of your engineering teams. See how engineering teams perform compared to the previous sprint, month, or quarter. View how work dynamics shift over time.

The Team Progress feature enables you to compare your teams’ performance indicators. You can choose which teams to compare, which repositories to compare, and the time frame of the analysis. The performance indicators included in the Team Progress report are:

Impact; - Impact is a way to measure the amplitude of code changes that are happening in a more complex manner rather than measuring raw lines of code. Impact is a measure of work size that takes this into account. Impact takes the following into account: | What percentage of the work is edited to old code. | The surface area of the change (think 'number of edit locations'). | The number of files affected. | The severity of changes when old code is modified. | How this change compares to others from the project history.
Efficiency; - It is the percentage of an engineer’s contributed code that’s productive, which generally involves balancing coding output against the code’s longevity. Efficiency is independent of the amount of code written.The higher the efficiency rate, the longer that code is providing business value. A high churn rate reduces it.
Active Days; - They represent any day where an engineer contributed code to the project.
Commits/Day; - It represents the amount of commits done by the developer in a day
New work; - It represents the amount of new code written.
Legacy refactor; - Legacy Refactor is the process of paying down on “technical debt”. The process of improving the structure of an old or unfamiliar code without changing its functionality
Help others; - It describes how much an engineer is replacing another engineer's recent code - less than 3 weeks old.
Churn code. - Churn code is when a developer re-writes their own code shortly after it has been checked in - less than 3 weeks old.

The pull request metrics analyzed in the Developer Progress feature are:

Total PRs; - It represents the number of pull requests created by an engineer.
Merged PRs; - It represents the number of merged pull requests of an engineer.
PRs Merged without Review; -I t represents the number of pull requests merged without review by an engineer.
Closed PRs; - It represents the number of closed pull requests of an engineer.
Open PRs; - It represents the number of open pull requests of an engineer.
PRs without Comments; - The total number of Pull Requests that have no comments.
PRs without Reviews; - The total number of Pull Requests that have no reviews.
Total PRs Comments; - The total number of comments in all Pull Requests.
Total PRs Reviews; - The total number of reviews in all Pull Requests.
PRs Merged without Rebase; - The total number of Pull Requests merged without a rebase.
Avg. Comments/PR; - The total number of comments per Pull Request.
Avg. Time to First Comment; - Avg. Time to First Comment is the average time between when a Pull Request is opened and the first time an engineer comments.
Avg. Time to First Review; - Avg. Time to First Review is the average time between when a Pull Request is opened and the first time an engineer reviews the pull request.
Avg. Time to Merge from Create; - Avg. Time Merge from Create is the average time from a Pull Request creation to it being merged.
Avg. Time to Merge from First Commit; - Avg. Time Merge from First Commit is the average time from a Pull Requests first commit to it being merged.
Avg. Time to Merge from First Comment; - Avg. Time Merge from First Comment is the average time from a Pull Request first comment to it being merged.
Avg. Time to Merge from First Review; - Avg. Time Merge from First Review is the average time from a Pull Request first review to it being merged.
Avg. Time to Issue PR from First Commit. - Avg. Time to Issue PR from First Commit is the average time from the first commit to creating a PR.
Avg. Time to Deploy from Merge. - Avg. Time to deploy since the Merge happened.