Last 90 days · Feb 2 – May 3
Average per-developer ETV across all 6 organizations. Median forecast lands on 300 ETV / dev by Q4'30 (current quarterly growth +29.8%). Three nested cone layers fan out around it. Click an organization in the legend to hide its line.
Math model
S-curve · slow start, accelerates, plateaus
We can measure your organization too — and help bend the trend in the right direction.
How we measureThis dashboard tracks engineering Performance — how much substantive work the team ships. We measure it in ETV (Engineering Throughput Value): every merged commit is scored by the depth of work it represents, and those scores add up to Performance. Higher Performance means more substantive output, not just more commits.
Performance breaks down into three work types — Growth (new functionality), Maintenance (refactors, tests, upkeep), and Fixes (bug-fix rework) — colored consistently across every chart.
How Performance is measured →Each organization contributes independently to the aggregate. Cards below summarize per-organization level and trend; the table immediately after lists totals per quarter and the change versus baseline.
Aggregate performance score per organization, by quarter. Unit: Engineering Throughput Value (ETV).
Where the team's monthly Performance went, averaged over the last 90 days. A larger Growth slice means more time on net-new features; a larger Fixes slice means more time reworking past code.
Total Performance per connected organization, in ETV, stacked by work type. Bar lengths compare engineering output across orgs; colors show what kind of work fills it.
Per-engineer ETV by week across the last 90 days. Each point is what the average engineer in the cohort contributed during that week; sum the points and divide by months to reconcile with the monthly rate in the card above.
Rolling 90 days Performance per connected organization. Δ compares the two most recent 90 days windows.