Mike Spitz: agents replace standups
- Mike Spitz of PFF said on April 10, 2026 that AI agents are pushing engineering teams away from daily standups and toward supervision workflows. - Spitz told AI Engineer Europe that PFF ran a three-month case study where two engineers shipped five times a day against ten engineers shipping once. - The talk video, “Agents Don’t Do Standups,” is available on YouTube, and AI Engineer Europe’s schedule lists Spitz’s April 10 session.
Mike Spitz used a conference talk in London on April 10 to argue that AI agents are changing the basic management routines of software teams. Spitz, identified by conference materials as speaking for PFF, said the company’s engineering work is moving away from daily standups and sprint rituals toward systems that supervise, evaluate and constrain agent behavior. The presentation, posted to YouTube in recent days, framed the change as an organizational redesign rather than a coding-speed upgrade. AI Engineer Europe’s published schedule lists the session as “Agents Don’t Do Standups: Building the Post-Engineer Engineering Org.” ### What did Spitz say replaces the standup? Spitz said the replacement is not a single new meeting but a workflow in which software agents handle more implementation work and humans monitor outputs, failures and approvals. The YouTube posting for the talk says PFF ran a three-month case study comparing “two engineers against a team of ten” on the same codebase and customer set. It says the two-engineer group shipped “five times a day,” while the 10-person team shipped “once.” (youtube.com) The daily.dev summary of the talk said PFF removed standups, sprint planning and retrospectives in favor of “bi-daily huddles,” automated ticket creation and a “spec-to-LDD-to-PR pipeline” driven by agents. That account said ticket status was tied to pull-request state, reducing the need for engineers to report progress manually. (youtube.com) ### What was the evidence behind the claim? PFF’s case study, as described in the conference video listing and third-party summaries, compared a two-engineer team using agentic workflows with a 10-engineer team working more traditionally. The daily.dev summary said the smaller team produced 25 times as many deploys and roughly 10 times the output, measured with ticket volume and complexity, while finishing a project expected to take four months in under two months. (app.daily.dev) An 8.6 out of 10 customer satisfaction score was one of the metrics highlighted in summaries of the talk. StartupHub.ai, which reported on the session after the event, said Spitz presented the results as evidence that the bottleneck in software delivery had moved from human coding time to specification quality, orchestration and review. That characterization is StartupHub.ai’s summary of his remarks. (youtube.com) ### If agents write more code, what do managers and engineers do? Spitz’s talk emphasized control systems around the agents rather than unrestricted delegation. The preliminary materials and published summaries point to evaluation loops, permissions for tool use, observability, retry and failure handling, and human override points as the core operating model. In that setup, engineers spend more time defining specs, checking system design, setting constraints and reviewing exceptions. (startuphub.ai) The daily.dev summary said code review was split by task, with agents handling style and naming checks while humans focused on architecture and higher-level design questions. It also said lightweight design documents, or LDDs, became a key stage before tickets and pull requests were generated. ### Why did Spitz describe this as an organizational change, not a tooling upgrade? (app.daily.dev) AI Engineer Europe scheduled Spitz’s session under a talk title that explicitly referred to the “post-engineer engineering org,” not an individual developer productivity tool. The conference listing places the talk in a broader event focused on AI engineering practices, and StartupHub.ai reported that Spitz described agents as changing backend orchestration and operational responsibilities across the team. (app.daily.dev) That framing matters because the processes under discussion included planning, ticketing, deployment and review, not just code generation. The third-party summaries say PFF’s workflow moved work upstream into specifications and design docs, then downstream into automated state changes and deployments, with people kept in the loop for approvals and exceptions. (ai.engineer) ### Where can readers check the talk and the source material? AI Engineer Europe’s schedule page lists Mike Spitz’s session on April 10 in London, and the conference site says the event ran from April 8 to April 10, 2026. YouTube hosts the talk under the title “Agents Don’t Do Standups: Building the Post-Engineer Engineering Org — Mike Spitz, PFF.” As of this week, the video page excerpt still carries the case-study line comparing two engineers with a team of ten on the same codebase and customers. (app.daily.dev) (ai.engineer)