A senior engineer waits three days for review on a pull request an agent wrote in eight seconds. A product manager ships six experiments in a quarter and cannot say which two mattered. An engineering manager runs a PI plan whose forecasts fall apart in the second week, and the team agrees not to mention it.
If any of this looks like yesterday, you are not imagining the friction. You are seeing what we are seeing.
The cost of producing a working first cut of almost anything has collapsed. The set of people who can produce one has widened beyond engineers. A PM, a designer, an analyst, a support lead can now put working software in front of a stakeholder before the conversation about whether to build it has finished. None of this is hypothetical. It is happening in your organization this week.
The bottleneck moved. Our processes did not.
Story points stopped predicting anything the moment one task took eight seconds and the next still took a week. Sprint commitments forecast a constraint that is gone. Definition-of-done as a team-owned checklist cannot bind an artifact produced from outside the team. PI planning batches a planning step whose marginal cost is now near zero. The three-day code review on an eight-second pull request is not coordination — it is the new bottleneck wearing the old one’s clothes.
These were good answers to real problems. The problems they solved are not the problems we have now.
What is scarce now is what was abundant before. Judgment about what to build. Attention to what we shipped. The discipline to validate honestly. The courage to stop. Production used to absorb most of our process design; with production receding, the parts of the work that always mattered — and that we always under-resourced — are what we are left holding. The work did not get easier. It moved.
Because we can now create production ready atfiacts at unprecedented speed, here is what we have come to believe.
Evidence, not shipping, is what closes a change. Done used to mean the code merged. Done now means we know whether it worked, and we have written down what we learned if it did not.
Reversibility is the new pace. We invest as much in our ability to undo a change as in our ability to make one. Shipping faster makes this matter more, not less.
Stopping is a first-class outcome. Killing a bad project matters as much as shipping the right one, and we measure ourselves on both.
The standard (acceptance) binds the artifact, not the producer. Whoever built it — engineer, designer, agent — the artifact meets the standard before it lives in production. Standards belong to the organization, not to the team that happens to be near the work.
Judgment, not output, is the senior craft. Producing a working first draft is no longer the hard part — anyone, or any agent, can do it. Deciding what to approve, what to send back, and what to throw out is. Our process should be designed around that judgment, not bolted onto a pipeline still tuned for production.
The team includes the agents. Our standups, our reviews, our retrospectives all assumed the team was a list of people. The work itself is now a blend of human and AI effort, and our process has to model that integration as deliberately as we ever modeled handoffs between people.
We are not telling you Agile was wrong. It was right for the world it was built for. We are telling you that world has changed, and the frameworks we built to navigate it are starting to charge us a tax we cannot afford to keep paying.
We are also not telling you the answers are finished. Underneath this document is a body of work — a position paper, a proposed unit of work, a production standards model, a role and gating model, a revised cadence; all of which are in our GitHub project. It is not light reading. It is more honest than this document, and incomplete on purpose. The next moves get built by all of us, in the open, or they do not get built well at all.
If you see what we see, sign with us. Forward this to the people you plan and execute with. Argue with us where we are wrong. The work begins when the document gets shared. Join the discussion and read the full documents over in our GitHub project.