Response Time is a part of the overall Cycle Time. Response is the period of time between the end of Development Time and the time by which the original developer gets feedback for their work.

Average Response Time shows the time it took for a PR to get a response from the time it was visible to the whole team.

When segments are placed together, Average Response Time shows the weeks in which your Response times were higher or lower than other weeks and higher or lower than the Industry Benchmark. Lower Response Time indicates that the team is quick to pick up review work, while increasing Response Time could lead to blocking issues and increase context-switching.

Average Response Time is a great comparison tool within Response Time that doesn’t drill down to anything else but is powerful by itself.

The Distribution of Response Time metric compares the number of Pull Requests (PRs) per Response Cycle to the amount of Time it took to complete said Response Cycle.

Distribution of Response Time shows where the team may have overloaded themselves with too many PRs. Slow review may be caused by large code changes or lack of expertise in this area. Highly collaborated team usually take less than 2 hours to provide initial feedback. Distribution can also show which PRs can be classified as outliers.

The Distribution of Response Time metric is a good way to find how often the team is overloading itself by checking how many Response Cycles are classified as dangerous.

Please note that the Industry Benchmark for Response Time is 24 Hours.