Content Comparison

Definition (Hover Text)

Pickup time measures the time a pull request waits for someone to start reviewing it. Low pickup time represents strong teamwork and a healthy review

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Line

Y Axis - Hours

X- Axis - Days/Weeks/Months

Filters

Branch Filter

Hover Format on KPI

Pickup time -<Hrs>

No. of MRs - <y>

Fields on Overlay

Project

Repository URL

Branch

Days/Week

Pickup time (In Hrs)

Business Logic

Calculation Formula

It is calculated as the difference between the two timestamps of open and first code review submission events of a Pull Request - in days.The shorter this pickup time, the more it demonstrates that the squad prioritizes code reviews efficiently. A pickup time under 1 day (on average) ensures that no pull request gets stale for more than 24 hours.With this metric, we can also compare the coding productivity of the engineering organization over time from for multiple tech stacks, independent of process differences. Tracking this metric over time can help us understand how the organization’s coding capacity is evolving.

Pull Request (PR) Pickup Time (PRPT) = PR_first_update_date - PR_creation_date

Trend

Decreasing Pickup time is a Positive trend

Maturity Levels

M1 : > 48 Hours

M2 : 16 - 48 Hours

M3 : 8 - 16 Hours

M4 : 4-8 Hours, 

M5 : <4 Hours

Instance level thresholds

Configurations

Processor Fields

KPI Specific fields

Target KPI Value

How to Validate KPI

Suggested ways of working

Sample JQLs

Benefits of KPI

How does the KPI help