Recorded webinar · Thursday, September 17, 2026
How do you turn individual developers using coding agents into a team that can ship predictably?
Agents made the coding work faster. They did not make software delivery a solo sport. Decisions can still disappear into sessions and promising prototypes remain hard to hand off, especially when teams move into production or modernize existing systems.
See how to build a dependable agentic engineering team, from shared intent through implementation, validation, and delivery.
David Judd
Founder & CEOCodeLantern
David has spent over two decades helping engineering organizations navigate major shifts in software delivery. At CodeLantern, he helps teams make agentic development dependable and maintainable in real delivery work.
The session
A practical view of what changes when individual agent use has to become a dependable team practice, from early intent through production and retained project knowledge. The recording includes the live audience Q&A.
Why faster code generation makes alignment, coordination, and shared understanding more important.
What must change when an agent-built prototype moves toward production or agents begin working inside an existing system.
How people and agents can align on intent and approach before substantial implementation is delegated.
How work, decisions, and project knowledge remain useful beyond the original developer and agent session.
A practical walkthrough of the artifacts that keep implementation legible, reviewable, and connected to the team’s original intent.
After the session
The complete recording and the Agentic Team Readiness Checklist are publicly available.
The full session, delivery-artifact walkthrough, and audience Q&A are available on demand.
Assess your team’s readiness and identify gaps across shared work, collaboration, delegation, durable knowledge, and performance measurement.
For the whole team
This webinar is for technology and engineering leaders responsible for turning coding-agent adoption into a dependable way of delivering software, and the senior practitioners who will make that operating model work.
Leaders accountable for delivery performance, investment, risk, and the operating model around software engineering.
Senior practitioners shaping how teams adopt agents while preserving review, shared context, and production quality.
Trying to move a promising agent-built prototype toward production.
Introducing agents into a modernization initiative inside an existing system or established codebase.
Seeing individual success that does not automatically translate into practices that scale across a team.
Reconsidering an overly autonomous approach after defects, weak understanding, or maintainability problems have emerged.
Watch on demand