Independent newsroom The Wyre News Network OpEd desk

Perspective 4 min read

Has Claude Killed SCRUM?

An engineer with Claude now ships a sprint's worth of tickets before planning ends, so the question is fair / and we sell SCRUM delivery, so we have to answer it honestly. What agentic AI actually killed, what it made more valuable, and what a delivery cadence looks like when construction is no longer the constraint.

By Brian Pandorf for the Wyre OpEd desk

Somewhere right now, a team is sitting in sprint planning, estimating story points for a feature that an engineer with Claude could ship before the meeting ends.

We sell SCRUM delivery. It is on our homepage, one of our six practices. So when we ask whether agentic AI just killed it, we are asking about our own inventory / and the honest answer is more interesting than yes or no.

Why the question is suddenly fair

SCRUM was engineered for a world with one defining constraint: building software was slow, and coordinating the humans who built it was expensive. The two-week sprint, the story-point estimate, the daily standup, the burndown chart / every ceremony exists to manage the gap between deciding to build something and having it built.

Agentic AI collapses that gap. A developer pairing with Claude ships in an afternoon what used to be a sprint's worth of tickets. The backlog item that earned a solemn eight-point estimate on Tuesday is deployed Wednesday morning. When construction stops being the bottleneck, a framework built entirely around metering construction starts to look like a ritual searching for a purpose.

And teams feel it. The standup where everyone reports on tickets that were finished an hour after they were opened. The sprint review demoing work stakeholders already saw in staging ten days ago. The velocity chart that has gone vertical and stopped meaning anything. If your ceremonies feel increasingly performative, that is not your imagination. The constraint they were built to manage is dissolving.

What Claude actually killed

Estimation as a discipline. Story points were always a proxy for human effort and human uncertainty. When the effort is machine-scaled, arguing whether a task is a three or a five is astrology. The honest modern estimate for most well-specified tickets is "today, if we decide it matters."

The standup as a status report. Reciting yesterday's progress made sense when progress was invisible without the recitation. Now the diff, the deploy log, and the dashboard are the status report. A meeting that repeats what the tooling already shows is theater with attendance tracking.

The sprint as a shipping container. Batching work into two-week crates was a concession to coordination costs. When a feature can go from ticket to production in a day, holding it hostage to a sprint boundary is not discipline. It is inventory sitting in a warehouse you no longer need.

Velocity as a health metric. Output volume was always a flawed measure. Now it is a meaningless one, because output is nearly free. Congratulating a team on shipping more tickets in the age of Claude is congratulating a factory on running its conveyor belt.

What Claude conspicuously did not kill

Deciding what to build. The constraint did not disappear. It moved. When building is cheap, choosing becomes the expensive skill, and the backlog stops being a queue of waiting work and becomes the single most consequential document in the company. Prioritization, sequencing, saying no / SCRUM's product-ownership discipline is worth more now, not less.

Verification and judgment. Claude produces work at a rate no review process was sized for. Someone still has to decide whether the thing is correct, on-architecture, secure, and worth keeping. The definition of done, the review gate, the acceptance criteria / the unglamorous quality machinery of SCRUM is now the actual bottleneck, and teams that deleted it are discovering what unreviewed machine-speed output does to a codebase.

The feedback loop. SCRUM's core idea was never the standup. It was empiricism: build a slice, inspect it, adapt. That loop does not become obsolete when iteration gets faster. It becomes the whole game. A team that can ship fifty experiments a month needs more rigor about inspecting and adapting, not less, or it just accumulates fifty unexamined bets.

The cadence of accountability. Stakeholders still need a rhythm where work is demonstrated, direction is challenged, and the team commits to what happens next. Whether that rhythm is two weeks or two days is negotiable. That it exists is not.

What delivery looks like now

The teams getting this right are not abandoning SCRUM. They are re-deriving it from first principles under the new constraint, and what comes out looks familiar but runs hotter.

Sprints compress / a week, sometimes days / and they are scoped around validation, not construction: not "how much can we build in two weeks" but "what do we need to learn before we build the next thing." Standups become decision meetings: blockers, tradeoffs, and what not to build, because status lives in the tooling. Refinement gets promoted from chore to centerpiece, because a crisply specified ticket is now the difference between an agent shipping the right thing by lunch and shipping the wrong thing at scale. And the retro survives untouched, because the failure modes are new and the only way through them is the inspect-and-adapt loop SCRUM was always secretly about.

Our verdict

Claude did not kill SCRUM. It killed agile theater / and it killed it dead. Every ceremony that existed to make slow work visible, every estimate that dressed up a guess, every meeting that performed progress instead of producing it: gone, and good riddance. What survives is the part that was always the point / empirical, accountable, tightly-looped delivery / and that part just became the most valuable discipline in software.

The uncomfortable truth is that AI did not change what good delivery is. It removed the excuse for not doing it. Teams that ran SCRUM as ritual are now visibly running rituals. Teams that ran it as an operating system for decisions are shipping faster than they have ever shipped in their lives.

So: has Claude killed SCRUM? Only the parts that deserved it.

Related Reading

More Opinion

From the same desk

Perspective

A Rounding Error

Over twenty-four hours the single largest AI crawler on one consultant's website arrived roughly 1,500 times under a nonprofit research archive's name, sent back nothing, and asked for his SSH keys, his AWS config and his Firebase service account key. Across a hundred such paths: 1,028 requests, 6.7 megabytes, zero referrals, and requests for anything he had actually written rounding to nothing. It appeared in no security log, because security logs record rule trips and he was not blocking it. It appeared in exactly one place: the AI crawler dashboard, counted as an audience. Cloudflare's CFO says humans will be a rounding error on the internet within five years and admits he has been wrong every time, always low. Machine traffic passed human traffic in May 2026, two years earlier than the company forecast. Why robots.txt is a request that OpenAI's own documentation says may not apply, why blocking the obvious way costs you the visibility and keeps the fetches, what it means that agent config files are now on the standard secret-scanning wordlist, and the afternoon of work almost no company has done.

13 min

Perspective

Cut The Price Last

When demand softens, the first lever everybody reaches for is price. It is also the most expensive lever on the board, the hardest to reverse, and almost never the one that was actually broken. Redfin reports buyers have negotiating power across most of the country, the median housing payment fell to $2,575 because sellers cut asking prices to a one-year low, and pending sales hit their lowest since early April. Underneath it, July payrolls came in at minus 23,000 against an expected plus 83,000 with another 103,000 revised away. So the softening is real, and the question is which lever you pull and in what order. Why cutting price assumes a diagnosis you have usually not earned, the cheaper levers ranked, why the gap between the decision and the execution is where the margin leaks, and the measurement problem underneath all of it: cost per lead holds beautifully steady while cost per closed sale doubles.

6 min

Perspective

The Layer Nobody Looks At

A man in Connecticut typed instructions into his own court filing in three-point white text on a white background, where no judge would see them and any software would. They told the system to agree with him and to disregard the court's earlier denials. He was caught, warned, did it again, and lost his e-filing privileges. In the same seven days Google made the visible watermark on its AI images optional while keeping the invisible one, Anthropic shipped an API letting third parties detect text its models probably wrote, a new benchmark found that no frontier model clears sixty percent on basic visual perception with counting, localization and OCR among the weakest skills, and OpenAI started turning Mac users' clicks and keystrokes into a searchable memory their assistant can read, while warning in its own documentation about prompt injection. Five stories, one story. Every document, image and screen you produce now has two readers and they do not see the same thing. What the judge worked out on his own about where these attacks get caught, why provenance just moved into the layer humans cannot check, what a watermark hit actually proves and why a clean result proves nothing at all, and the ten-line diff almost nobody runs.

18 min