How does Uplevel define PR/MR Velocity?
PR/MR Velocity counts the number of merged PRs/MRs a group has collectively authored in a given time period, normalized by the group size and number of weeks in the period. It is an indication of how frequently code changes occur, and whether that comes in a consistent cadence. PR/MR Velocity is helpful for all teams to better understand their ability to consistently deliver code.
Complexity is calculated by looking at the number of lines added and deleted, number of files, and language that indicates potential refactors. Each PR/MR is estimated to be either “Complex” or “Not Complex” to review in this metric.
Two factors determine whether a PR/MR has become “delayed”—the Complexity, as well as time spent in the Waiting / In Review phases. For example, a “Not Complex” PR/MR would be considered delayed if it was under review for more than 2 working days.
A PR/MR is considered to include a test if at least one file changed contains the word test in the full file path.