Size vs time plots the relationship between pull request size (lines changed) and cycle time (time from open to merge). It helps you see whether larger PRs are taking disproportionately longer to land, which is one of the most common sources of delivery slowdowns.Documentation Index
Fetch the complete documentation index at: https://docs.periscope.sh/llms.txt
Use this file to discover all available pages before exploring further.
What Periscope tracks
The dashboard shows a scatter plot of merged PRs in the selected time range, with:- X-axis — PR size (additions + deletions)
- Y-axis — Cycle time (hours from open to merge)
- Each point — an individual merged PR
Interpreting the data
The expected pattern
In most teams, larger PRs take longer to merge. A visible upward trend from left to right is normal. The question is how steep the curve is:- Gentle slope — larger PRs take somewhat longer, but the team handles them well. Review capacity is healthy.
- Steep slope — large PRs take dramatically longer. This is a sign that big changes create review bottlenecks.
- Flat — PR size does not significantly affect cycle time. This is unusual and may mean the team is rubber-stamping large PRs or has very fast automated review processes.
Outliers
Look for PRs in the upper-right quadrant (large and slow). These are the most impactful to investigate:- Were they blocked on review?
- Did they require multiple rounds of feedback?
- Could they have been broken into smaller PRs?