As AI coding assistants and autonomous agents become standard across the software development lifecycle, engineering organizations face a critical question: how do we meaningfully measure developer productivity? Traditional vanity metrics like lines of code, pull request counts, or the percentage of AI-generated code often create perverse incentives without reflecting actual business value or software health.
This hands-on, interactive workshop equips engineering leaders, platform engineers, and practitioners with a structured method to define metrics that actually matter. Participants will deconstruct high-level goals into clear concepts, input drivers, and measurable proxies. We will explore how to balance delivery throughput, system stability, cognitive load, and user-centric outcomes in an AI-assisted engineering environment.
DORA Lead & DevOpsDays Global Organizer, USA
Sustainable DevOps in the Agentic AI Era explores how AI is evolving from a coding assistant into an active participant in software delivery and production operations. The workshop introduces practical approaches for building AI-powered DevOps workflows using agents, RAG, tool calling, agentic workflows, observability, evaluation, guardrails, and human-in-the-loop controls. Through enterprise-inspired scenarios, participants will learn how to adopt Agentic AI while maintaining reliability, security, governance, and cost efficiency—building AI systems that can be trusted in real-world DevOps environments.
Software Testing & Quality Assurance Dept. Head, ITI, Egypt
Executive Manager | MCIT – ITI, Egypt
Chief Software Architect - Tek Caffe, Egypt
The activities of software development have barely changed. Requirements, design, build, test, operate: the same five have appeared in every model since the 1950s, from Waterfall through Agile to DevOps. What changed each time was not the work but who does it, in what order, and alongside whom.
AI agents are the next shift of that kind. They now write code, generate tests, produce pipelines, and propose fixes. But which of these activities should they lead, and which still belong to us? How do we decide, and on what basis? Most teams answer case by case, and the inconsistency shows up as agents drifting without direction, outputs nobody fully trusts, and changes nobody can explain after they ship.
This workshop introduces the Human–AI Lead Map, a taxonomy that places every activity in the delivery lifecycle according to who leads it. It covers software development practices and extends across DevOps and DevSecOps: pipelines, infrastructure, security gates, observability, and incident response. Through engaging exercises, attendees will place real activities on the map themselves and leave with a clear view of where that line sits in their own organization.