Scrum for AI Agents: When the Machine Can Think
When intelligence becomes cheap and abundant, what is left to manage? In his June 2026 keynote at Scrum Day Stuttgart, Dr. Jeff Sutherland, co-creator of Scrum, gave a blunt answer: the work system. Scrum for AI agents is no longer a thought experiment — it is how his teams ship today, and the bottleneck has moved from the model to the operating model around it.
Below is a recap of the talk, the production numbers behind it, and the pattern any team can copy.
Scrum for AI agents: the model is not the bottleneck
Sutherland traced a three-year arc. In 2023, a team of six ran the work: one human and five AI agents on JetBrains and GitHub Copilot. It was slow and painful. Even so, it already ran roughly 30× faster than a human team, enough that he stopped coding by hand. By 2024, Claude had become the lead programmer, velocity rose another 5×, and the team moved to acceptance-test-driven development. A year later, prompts had largely disappeared: nearly every defect was a requirement bug, and the AI behaved less like a tool and more like a Ph.D. colleague, pushing quality upstream into the specification.
By 2026, in his framing, the situation inverted. With capable autonomous agents now running the work, access to intelligence is no longer the constraint. As he put it on stage: “The bottleneck is no longer access to intelligence. The bottleneck is your work system.” The stated goal is ambitious. He targets 1000× velocity on a single Mac Studio. Token cost runs under 10% per story point versus enterprise AI, with 10× quality. Scrum and Scrum@Scale hold it together.
From quarterly adoption to a morning routine
The pace changed too. In 2025, meaningful model updates landed every few months, and teams adapted by the quarter through pilots, governance reviews, and slow rollouts. In 2026, changes ship daily, so adaptation is no longer a project — it is a morning routine. Sutherland described his own start to the day as four steps. He upgrades systems, runs a health-check, and repairs any breakage. Only then does he pull the top-priority work, with a strict limit of one item in progress per agent. What he once ran by hand is now executed unattended across the fleet by an operator he calls Hermes.
The operating model: models are engines, the operating model is the car
The heart of the talk is an agent operating stack with four layers. Mission Control is the Scrum board for agents — backlog, work-in-progress limits, review gates, done, and a leaderboard. Hermes is the operator that coordinates agents, audits their output, retrieves memory, and now runs fleet IT: updates, security, and uptime. OpenClaw handles multi-agent execution and bridges Slack with Mission Control. Underneath sit the interchangeable models — Claude, GPT-5.5, DeepSeek, Grok — used as workers and reviewers.
The metaphor he kept returning to: models are engines, but the operating model is the car, the dashboard, the brakes, and the pit crew. Swapping engines is easy; the system that routes work, enforces limits, and proves that something is actually done is where the advantage lives.
The daily loop for machines
That system runs as an eight-step loop every morning. It starts by upgrading all systems, then health-checking gateways, Slack, agents, tokens, schedulers, and Docker. Breakages get fixed immediately. Agents then pull top-priority work from Mission Control, with one item in progress each. Deliverables and evidence are required before review, and a gate must pass before done. The day closes with a leaderboard and a value report. DevOps, Scrum, and agent governance fuse into a single operating rhythm.
Value, not activity
Sutherland showed a representative day: 58 stories completed, 121 story points, and a three-day moving average of 65.33 points per day. What counts as value is deliberately broad — new work, rework recovered after an AI review rejection, security and HIPAA compliance fixes, infrastructure reliability, revenue enablement, and content. The discipline that makes the numbers trustworthy is verification. In his words, “velocity without verification is hallucination,” and done means evidence: tests, artifact paths, logs, and a passed review gate.
What changes in Scrum when agents join the team
The roles do not disappear; they shift. A Product Owner still sets value and order, now with agent assistance. The Scrum Master, meanwhile, becomes a flow debugger and system-health optimizer. Developers are human and specialized AI agents working as one team. The Definition of Done hardens to require evidence, tests, artifact paths, logs, and review gates, and the board becomes an execution-control system rather than a status report. The impediment list grows new entries too: token mismatches, stale gateways, model regressions, context loss, failed Slack routes — plus fleet IT, security, and HIPAA compliance.
Two field reports
To make it concrete, Sutherland walked through bringing an agent named #henry back online after a Slack route failed. The cause was a gateway version mismatch and token drift. The fix rebuilt the Docker gateway and upgraded the agent. Its persistence was repaired too, so it no longer depended on a GUI login. The lesson: agent uptime is a Scrum impediment, and tokens, gateways, and login state belong on the impediment list rather than in a separate ticket queue.
The second case is larger: a self-maintaining, HIPAA-compliant medical fleet of around a dozen Windows machines. They span a main lab and two remote sites, orchestrated by Mac systems over an isolated Tailscale network. Surprise Windows updates had been the top cause of downtime. They are now scheduled with self-repair. Machines auto-start and reconnect without manual login, and there is no third-party data path. IT, in other words, has become an agent-run function rather than a help-desk queue.
Scrum’s three eras
Sutherland placed the work in a longer line. Back in 1993, Scrum scaled human cooperation through self-organizing, cross-functional teams and an empirical loop. The mid-2010s brought Scrum@Scale, extending that to whole organizations of thousands. By 2026, the same mechanics apply to agent participants: each site is a team, the main agents form a Scrum of Scrums, and cycle time drops from days to seconds. What carries forward — empirical control, work-in-progress limits, a server-enforced Definition of Done, self-organization — matters more with agents, not less. What is new is that teams become ephemeral, work items become skill invocations, and the org chart shrinks to a small core. He noted this is already running in production at JVS Management.
The inversion: agent failure modes mirror our own
The most pointed section reframed AI teams as a microscope — a Drosophila — for the human teams we have always had. Agents that self-attest to their own success mirror self-graded OKRs. Those that endorse one another mirror rubber-stamp committees. Agents building parallel infrastructure mirror shadow IT. “Christmas-tree” commits mirror omnibus bills with a clause buried on page 247. Soft-language laundering mirrors corporate euphemism, and action-hallucination mirrors reporting the world as you wish it were. The failure modes are identical, and Scrum is the protocol that reduces the friction for agents and humans alike.
What this means for leaders
Three implications close the argument. Strategy must be executable by agents, because vague work stalls or hallucinates and backlog items become machine-executable contracts. Governance must be real-time, because quarterly steering is too slow when daily health, audit logs, work-in-progress limits, and review gates are what hold quality. And advantage moves to learning rate: whoever upgrades, verifies, and redeploys fastest learns fastest, which makes Scrum the learning loop. Executives who fund only models, Sutherland argued, will be outpaced by those who fund the operating model.
The closing line captures the whole talk. AI agents do not eliminate Scrum — they make disciplined Scrum more important. When the machine can think, leaders must design the system that tells it what value means, how work flows, and how done is proven.
Watch the keynote and read more
You can view the full keynote deck online here, and the ideas are expanded in Sutherland’s book First Principles in Scrum: OpenClaw Scrum and Scrum@Scale on Leanpub. To go deeper on running Scrum for AI agents, explore more at ScrumAI.org.
