Versions Compared

Version Old Version 3 New Version Current
Changes made by

Pranav Barar (Unlicensed)

Ananth Pal (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Definition (Hover Text)

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

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Line

Y Axis - Hours

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

FiltersBranch Filter

Branches & Developers

Hover Format on KPI

Pickup time -<Hrs>Duration: From Date - To Date
No. of MRs - <y>PRs: XX

Fields on OverlayExplore

  • Project

  • Repository

URL

  • Branch

  • Developer

  • Days/

Week

  • Weeks

  • Pickup

time

  • Time (In

Hrs

  • Hours)

Business Logic

Calculation Formula

It Pickup time is calculated as the difference, in days, between the two timestamps of open and when a pull request is opened and when the first code review submission events of a Pull Request - in days.is submitted.

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

TrendDecreasing

Pickup time is a Positive trendA decreasing trend is considered positive.

Maturity Levels

M1: > 48 Hours
M2: 16 - 48 Hours
M3: 8 - 16 Hours
M4: 4-8 Hours, Hours 
M5: <4 < 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.