MR throughput, cycle time & allocation —

Overall vs BE vs SET, month over month. Sourced directly from app.getdx.com — BE/SET use the Engineering Craft attribute (Backend / Testing).

MR throughput — merged MRs per active engineer / week

Higher is better. Overall climbed from trailing Industry P75 by ~47% in the year-to-date view to +16% above P75 by June.

MR cycle time — hours from open to merge

Lower is better. All three groups roughly halved cycle time from April to June.

Time in status — average days per active-work stage

In Progress, In Review, Ready for Testing, and Testing — the active-work stages, month over month.

Work allocation — Overall share of merged MRs by type

Maintenance / Fixes / Features, month over month, against fixed targets.

Maintenance Fixes Features

Data sources: all figures sourced exclusively from DX (app.getdx.com) via Playwright automation — no manual sheet involved. Team ; BE/SET via Engineering Craft attribute (Backend id 49514 / Testing id 49511). Throughput: dx-throughput.js → pr-throughput?metric=weighted. Cycle time: dx-cycletime-workhours.js → pr-cycle-time with Settings → "All hours" OFF (working hours only; toggles back ON on every page load — the script re-applies it each run). Allocation: dx-allocation.js → pr-allocation; null Fixes treated as 0% (DX omits column when 0%). Time in status: dx-time-in-status.js → time-in-status with Settings → Week + Median; filtered via jira_statuses to In Progress / In Review / Ready for Testing / Testing.