Team Summary

The Team Summary provides a comprehensive report of an individual team's work patterns for a specific period.

This feature provides users with valuable insights into daily Code Commits, New Work vs. Churn to determine if the team is stuck and the identification of each team member's strengths and areas for improvement. The Team Summary is a great way to track and monitor team progress, making it easier to identify weaknesses and find opportunities for growth.

Zoom into any metric displayed in the Team Summary report by clicking "More".

After clicking "More", you'll see a modal containing a graph of the metric you selected.

What does the Team Summary report contain?

Cycle Time Breakdown

The Cycle Time indicates your team's velocity, and it has four stages:

CODING - Time to Issue PR from First Commit. This metric corresponds to the coding time and is the time elapsed from the first commit to creating a PR.

PICKUP - Time to First Review. This metric indicates how fast reviewers pick up their peers' PRs for review and is the time between when a PR is opened and the first time an engineer reviews that PR.

REVIEW - Time to Merge from First Review. This metric signifies how fast submitters incorporate feedback from their peers in code review and is the time from a PR's first review to that PR being merged.

DEPLOY - Time to Deploy from Merge. This metric is an indicator of how fast code gets deployed into production and is the time between when a PR is merged to when it gets released into production.

Commit Risk Breakdown

Commit Risk measures how likely a particular commit will cause problems. Think of this as a pattern-matching engine, where Waydev looks for anomalies that might cause problems.

Here are some of the questions we ask when looking at risk:

How big is this commit?
Are the changes tightly grouped or spread throughout the code base?
How serious are the edits being made? Are they trivial edits or deeper, more severe changes to existing code?

Work Focus Breakdown

NEW WORK - Brand new code that does not replace other code.

LEGACY REFACTOR - The process of improving the structure of an old or unfamiliar code without changing its functionality (after 21 days)

HELP OTHERS - It describes how much an engineer is replacing another engineer's recent code (less than 21 days)

CHURN - Churn is when a developer re-writes their own code shortly after it has been checked in (the first 21 days)

Commit Breakdown

This is a breakdown of all the commits from the selected time frame. It includes the date and time of the commits, the commit message, and the work focus of the commit.
If you hover over the commit message, you will see the developer who made that commit and in what repository it was made. Once you click the commit message, you'll be redirected to the commit page in your Git provider.