Agile Analytics: measuring where the time goes in your software organisation

Ask an engineering team where the time goes and you rarely get the answer the data gives. Build times are on every dashboard; waiting on a review, a handover between teams, or an environment that is occupied appears nowhere. That is where most of the loss sits, and it is precisely what the screens you already have cannot show you.

Agile Analytics reads Git, CI/CD and Jira, and adds team surveys and interviews on top. That produces three lenses: AgileEx for the workflow, DevEx for the human factors, and OpsEx for system reliability. DORA and SPACE are in there, with SLOs and error budgets — but side by side rather than as loose numbers.

The answer is often not the one people expected. Jeroen Bultje of Maxeda, on what the measurement showed them: "We thought our bottleneck was deployment speed. It turned out to be handovers."

That is the kind of conclusion a team can spend months optimising the wrong side of. Deploying faster would have made no difference at Maxeda at all.

Agile Analytics reports lead times coming down by 30 to 60 per cent and 20 to 40 per cent fewer failed deployments. The arithmetic underneath is simple: thirty minutes of waiting per engineer per day works out at roughly €5,000 per engineer per year. At a hundred engineers that reaches half a million — a figure that appears on no invoice.