Developer | Pickup Time

Definition (Hover Text)

Pickup time measures how long a pull request waits before someone starts reviewing it. A low pickup time indicates strong teamwork and a healthy review process.

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Line

X Axis - Days/Weeks/Months
Y Axis - Count (Hours)

Filters

Branches & Developers

Hover Format on KPI

Duration: From Date - To Date
No. of PRs: XX

Fields on Explore

• Project

• Repository

• Branch

• Developer

• Days/Weeks

• Pickup Time (In Hours)

Business Logic

Calculation Formula

Pickup time is calculated as the difference, in days, between the timestamps of when a pull request is opened and when the first code review is submitted.

The shorter this pickup time, the more it demonstrates that the squad prioritizes code reviews efficiently.

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

Trend

A decreasing trend is considered positive.

Maturity Levels

M1: > 48 Hours
M2: 16 - 48 Hours
M3: 8 - 16 Hours
M4: 4-8 Hours 
M5: < 4 Hours

Instance level thresholds

20

Configurations

Processor Fields

Nil

KPI Specific fields

Target KPI Value

How to Validate KPI

Suggested ways of working

• Ensure accurate timestamps for when a pull request is created and when the first review begins.

• Ensure reviewers are assigned immediately to pull requests for accurate measurement of response time.

• Standardize the workflow for PR handling to ensure consistent data collection and avoid discrepancies.

Sample JQLs

N/A

Benefits of KPI

How does the KPI help

A pickup time of under 1 day (on average) ensures that pull requests are addressed within 24 hours, preventing them from becoming stale. This metric also enables comparison of coding productivity across different tech stacks, independent of process variations. Monitoring this over time helps assess how the organization’s coding capacity is progressing.