Europe 2026
Agents Don't Do Standups: Building the Post-Engineer Engineering Org — Mike Spitz, PFF
Overview
This talk explores a case study at PFF, a sports data company, where they transformed their engineering organization by integrating AI agents. The core thesis is that by shifting focus from optimizing individual engineer output to enhancing agent capabilities, significant gains in deployment frequency and product quality can be achieved. This approach led to a reimagining of traditional engineering processes, moving away from rigid structures like Scrum towards more agile, feedback-driven workflows.
Who should watch
- AI engineers looking to build more effective agentic workflows.
- Product Managers seeking to understand how AI can accelerate development cycles.
- Builders experimenting with agent-based development and process optimization.
- Teams struggling with slow development cycles and falling behind competitors.
- Organizations considering a shift away from traditional agile methodologies.
Key takeaways
- A two-engineer team leveraging AI agents achieved a 25x increase in deployment frequency compared to a 10-engineer team using traditional methods.
- AI agents were used to automate tasks like generating specifications, lightweight design documents, tickets, and PRs, streamlining the development lifecycle.
- Traditional ceremonies like sprint planning and daily standups were eliminated, replaced by more frequent, integrated feedback loops and automated status updates.
- Customer satisfaction scores improved significantly, with the AI-assisted team achieving an average quality score of 8.6 out of 10, up from 7-7.5 previously.
- The focus shifted from optimizing engineer output to making agents quicker and more capable, leading to a compounding increase in overall productivity.
- Agentic code reviews were implemented for tedious, opinionated tasks, allowing human engineers to focus on higher-level system design and architecture.
- A phased, slow approach is recommended for integrating AI agents, starting with the most curious engineers and non-critical systems.
- The new engineering model emphasizes verifiable, deterministic tasks and encoding team culture and patterns into agent skills.
Notable quotes
*The core question was instead of figuring out how we can help engineers go and output more, how do we help make the agents quicker?*
*It doesn't matter if the output's more. It doesn't matter if the number of deployments are higher. What really matters is basically if our customers are happy.*
*Engineers aren't the bottleneck. So, we don't need to have all the old ceremonies that we had before.*
Unofficial community note. Prefer the recording for nuance.