Published research
DORA Metrics: What They Show and What They Don't
DORA now tracks five metrics, not four. Here's what they measure, what they can't tell you, and why AI adoption is pulling throughput and stability apart.
4 related · metrics
Engineering measurement · Independent
What the frameworks actually measure, what the platforms actually cost, and where both stop being true. Every article states its evidential basis.
Published research
DORA now tracks five metrics, not four. Here's what they measure, what they can't tell you, and why AI adoption is pulling throughput and stability apart.
4 related · metrics
Published research
Core 4 folds DORA, SPACE and DevEx into four dimensions. Here's how it works, why 'diffs per engineer' is controversial, and where it still falls short.
4 related · metrics
Published research
SPACE says productivity is multidimensional and no single metric captures it. Here's how to apply it, and why its Activity dimension is now the weak one.
4 related · metrics
Published research
The framework that measures the lived experience of developers rather than the artefacts they produce — three dimensions, how to measure them, and its limits.
4 related · metrics
Published research
You can run DORA metrics without paying a vendor. Here's what's available, what each option costs you in engineering time, and when free stops being cheaper.
4 related · tools
Published research
Engineering analytics platforms split into two architectures. The difference decides what questions you can answer — and how long your security review takes.
4 related · tools
Documentation & public sources
Appfire Flow (ex Pluralsight Flow, ex GitPrime) reaches end of life 31 December 2027 and renewals closed 30 June 2026. The verified dates and how to pick a replacement.
4 related · tools
Documentation & public sources
LinearB automates the workflow. Swarmia measures the team and asks it to change. Which one fits depends on a question about your organisation, not your stack.
4 related · tools
Published research
Most vendors in this category hide pricing. Here's what buyers report paying, where the figures disagree, and how to read a quote before you sign one.
4 related · tools
Documentation & public sources
These two platforms answer different people's questions. Jellyfish is built for the CTO reporting to a board; LinearB for the manager fixing a review bottleneck.
4 related · tools
Published research
Your DORA dashboard went green after rolling out Copilot, and your engineers say they feel slower. Here's why both can be true.
4 related · ai-measurement
Published research
Two large 2026 datasets on AI-assisted code and maintenance burden — what they found, what they don't prove, and how to read them before quoting them.
3 related · ai-measurement
Published research
Four ways to work out how much of your codebase came from AI assistants — IDE telemetry, heuristics, commit provenance and surveys — and the failure mode of each.
3 related · ai-measurement
Published research
You've been asked for a return figure on AI coding tools. Here's a defensible answer, why the confident version is worse than the honest one, and what to bring instead.
4 related · ai-measurement
Published research
Six measures that were reasonable proxies until assistants changed what they proxy for — and what still holds up.
4 related · ai-measurement
Documentation & public sources
A new product category formed around one question boards are asking. Here's what the different architectures can and cannot establish.
4 related · ai-measurement
Published research
The argument against per-developer measurement, the 2023 debate that made it public, and the peer-reviewed research on what monitoring does to teams.
4 related · opinion
Published research
Seven ways a DORA dashboard produces confident, wrong numbers — and how to tell whether yours is measuring delivery or measuring your configuration.
4 related · opinion
Published research
Most engineering metrics programmes fail quietly: the data is fine, the dashboard exists, and nobody looks at it. Why that happens and how to fix it.
4 related · opinion
Published research
One set helps a team decide what to change this week. The other explains engineering to people outside it. Most programmes fail by trying to use one set for both.
4 related · opinion
Published research
Efficiency is output over input. Software development has neither a stable output nor a comparable input, which is why the frame keeps producing bad decisions.
4 related · opinion
Published research
Our testing process, data sources, funding and correction policy — so you can judge how much weight to give what you read here.
0 related · practice
Published research
A sequenced plan for introducing delivery metrics without triggering the resistance that kills most measurement programmes in month two.
4 related · practice
Published research
Platform teams ship to other engineers, so delivery metrics measure their customers rather than them. Here's what to measure instead.
4 related · practice
Published research
The conversation that determines whether a measurement programme works. What to say, what not to say, and what the research shows about framing.
3 related · practice
Independent work on engineering measurement. No vendor sponsorship, no affiliate placement, no weekly cadence padded with links.