2026-11-19
Story points measure volume. Measure validation instead.
Full text
Most teams still plan sprints in story points. Once an AI agent writes most of the code, I think that number stops telling you much.
Generating code got cheap. Checking that it's right didn't.
For 15 years I ran delivery where velocity was a decent proxy. Building was the slow, expensive part, so counting what got built made sense.
Now an agent can produce a feature in an afternoon. A team can double its points and, in the same sprint, pile up rework, drift between spec and code, and review debt that never shows up on the board.
So the question I ask a team has changed. How much of what you built was accepted the first time someone reviewed it?
Across the 70+ AI projects I've worked with this year, these are the numbers I look at, with the bar I set: - first-pass acceptance: 80% or more of agent output approved without rework - rework: under 20% of effort going back into work already marked done - validation latency: finished work waits less than 1 day for a person to check it
None of them reward volume. A team that generates faster than it can verify sees them slip within 2 or 3 sprints, long before velocity says anything is wrong.
When building is nearly free, judgement is the scarce resource. That's what the plan should measure.
If you run teams with agents in the loop: what replaced story points in your planning, if anything did?
#SoftwareDelivery #AIAgents #EngineeringManagement


