Measure
Developer Velocity
Read durable throughput trends alongside quality and rework context.
- Audience
- engineering leaders, managers
- Required role
- Manager or administrator with organization-wide Measure capability.
- Product access
- Measure
- Navigation path
- Measure > Developer Velocity
Outcome
Explain a durable throughput trend and investigate the work that changed it.
Before you begin
- Processed pull requests across the comparison period
Choose a time range
Select a window long enough to reduce the impact of a single release or holiday. Keep repository and team filters visible when comparing periods.
Read the trend
Velocity represents weighted, durable delivery rather than raw pull request count. Read it with quality, effort, and rework so generated or mechanical volume does not look like product progress.
Segment the result
Break the trend down by team, repository, or work category to locate the system that changed. Avoid comparing groups with different responsibilities as if the metric were a competition.
Investigate a change
Open the contributing pull requests and releases. Look for batch size, review delay, deployment cadence, quality, and rework patterns before choosing an intervention.