Why Agents Are Forcing Enterprises to Finally Fix Their Dev Process

Enterprises are finally being forced to care about their software development lifecycle — not because anyone suddenly got disciplined, but because agents cost money and the waste is now visible. When it was humans, it was "Timmy's just lazy." Now it's a line item.

Simon Maple sat down with Patrick Debois (the godfather of DevOps, now DevRel at Tessl), Tammuz Dubnov (co-founder and CEO of Autonomy AI), and Daniel Jones (Head of Product at re:cinq) at AI Native DevCon London for a wide-ranging panel on AI enablement — who owns it, what's breaking, and what the organisations getting it right are actually doing differently.

What we cover:

– Who should own agentic coding adoption inside an enterprise, and why platform teams are already filling the vacuum

– The "Timmy's lazy" problem: why agent cost visibility is forcing process discipline that humans never got

– Why PR-based workflows are an anti-pattern inside enterprises once you're moving at agent speed

– The PUMP framework (Plan, merge, polish): how one team is shipping features with developers, PMs, and designers all opening PRs –

Rethinking what a "test" is in an agentic world — and why feedback loops matter more than first-pass correctness

– The biggest mistake enterprises are making right now: piecemeal adoption with no mandate and no shared tooling

🌐 Tessl: https://tessl.io

🔔 Subscribe for weekly episodes on AI-native development

What's your team's approach to AI enablement — central mandate or letting individuals find their own way? Drop it in the comments.