2.0 -//Pentabarf//Schedule//EN PUBLISH P9SJNM@@talks.devopsdays.org -P9SJNM Registration, Sponsors, Breakfast - Day 1 en en 20260922T080000 20260922T090000 010000 Registration, Sponsors, Breakfast - Day 1 PUBLIC CONFIRMED Other https://talks.devopsdays.org/dodroxrox26/talk/P9SJNM/ Main Stage PUBLISH HA9EMA@@talks.devopsdays.org -HA9EMA When Production Burns, You're the Fire Department (and the Fire Marshal, Too) en en 20260922T091500 20260922T101500 010000 When Production Burns, You're the Fire Department (and the Fire Marshal, Too) Whether you're new to on-call or you've been running incidents for years, you'll leave with practical insights about responding to incidents, preventing them, and learning more from the ones that happen anyway, despite your best efforts. PUBLIC CONFIRMED Keynote https://talks.devopsdays.org/dodroxrox26/talk/HA9EMA/ Main Stage Brent Chapman PUBLISH XQVQKM@@talks.devopsdays.org -XQVQKM Coffee Break - Day 1 en en 20260922T101500 20260922T110000 004500 Coffee Break - Day 1 PUBLIC CONFIRMED Break https://talks.devopsdays.org/dodroxrox26/talk/XQVQKM/ Main Stage PUBLISH FDTEUK@@talks.devopsdays.org -FDTEUK Why Most SLOs Fail en en 20260922T110000 20260922T113000 003000 Why Most SLOs Fail This talk is drawn from direct SRE leadership and consulting work experience assessing SLO programs across engineering organizations of varying size and maturity. The failure modes described are ones I've observed repeatedly in the field- in organizations that had done everything "right" on paper and still saw no material improvement in production reliability. **Why this talk:** Most SLO content focuses on the technical implementation- how to define SLIs, calculate error budgets, and build dashboards. **That's not the problem.** Teams that have done all of that are still failing. **The gap is organizational, not technical, and it's rarely discussed.** Outline: * Why SLO programs fail even when teams do everything right * Four antipatterns observed firsthand that guarantee failure, regardless of tooling or effort * A maturity model for SLO programs- and why the jump from immature to minimal maturity isn't technical * What it practically takes to give reliability a seat at the table: exec commitment, enforced error budget policy, and product in the room * A five-question diagnostic practitioners can run **immediately** to assess where their organization stands **Audience takeaways:** * The reason most SLO programs fail isn't technical- reliability lacks organizational authority, and no dashboard fixes that * A concrete maturity model to locate where your organization actually is, not where you think it is * Five diagnostic questions to run at your next retro that will tell you everything about your SLO program's health Speaker background: ~20 years in tech, ~10 in DevOps/SRE. Seasoned public speaker. PUBLIC CONFIRMED Talk https://talks.devopsdays.org/dodroxrox26/talk/FDTEUK/ Main Stage Amin Astaneh PUBLISH ZEQ839@@talks.devopsdays.org -ZEQ839 When AI Agents Touch Real Infrastructure: Five War Stories and a Frameworkk en en 20260922T113000 20260922T113500 000500 When AI Agents Touch Real Infrastructure: Five War Stories and a Frameworkk PUBLIC CONFIRMED Ignite https://talks.devopsdays.org/dodroxrox26/talk/ZEQ839/ Main Stage Adam Gordon Bell PUBLISH UKQQRK@@talks.devopsdays.org -UKQQRK Question Everything: How Curiosity Strengthens Security en en 20260922T113500 20260922T114000 000500 Question Everything: How Curiosity Strengthens Security Lighting Talk: 20 Slides - 15 seconds each Slides 1-3 - Walk through “Question Everything” concept by Socrates Slides 4-8 - Real world examples of the impact of people asking simple questions which demonstrate global change. Slides 9-13 - What security questions are we not asking? Provide examples. Slides 14-18 - What the impact can be in asking the question that I am most interested in: Who is building the code within your software supply chain? Slide 19-20 - Encourage the audience to ask themselves simple and important questions. PUBLIC CONFIRMED Ignite https://talks.devopsdays.org/dodroxrox26/talk/UKQQRK/ Main Stage Amanda Aguayo PUBLISH VAQDC3@@talks.devopsdays.org -VAQDC3 For Want of a Clearly Written Sentence en en 20260922T114000 20260922T114500 000500 For Want of a Clearly Written Sentence PUBLIC CONFIRMED Ignite https://talks.devopsdays.org/dodroxrox26/talk/VAQDC3/ Main Stage Matt "Kelly" Williams PUBLISH Z8DCQ8@@talks.devopsdays.org -Z8DCQ8 Your CI/CD Pipeline Is About to Meet AI — Here's What It Doesn't Know en en 20260922T114500 20260922T115000 000500 Your CI/CD Pipeline Is About to Meet AI — Here's What It Doesn't Know A fast, opinionated 5-minute format: one failure mode per minute, drawn from documented production post-mortems and infrastructure gap analysis. The structure maps cleanly to the Ignite format — 4 slides per failure mode (the assumption, why it breaks for AI, what it costs, and the right question to ask instead). No tools, no demos — just the 5 mental model shifts every DevOps engineer needs before their first AI deployment. Designed to spark open space conversations rather than close them. PUBLIC CONFIRMED Ignite https://talks.devopsdays.org/dodroxrox26/talk/Z8DCQ8/ Main Stage Saideep Navakoti PUBLISH BKR3TS@@talks.devopsdays.org -BKR3TS Salvage Title Software: How Engineering Teams Ship to Themselves en en 20260922T115000 20260922T115500 000500 Salvage Title Software: How Engineering Teams Ship to Themselves PUBLIC CONFIRMED Ignite https://talks.devopsdays.org/dodroxrox26/talk/BKR3TS/ Main Stage Morgan Helton PUBLISH ZJGUZL@@talks.devopsdays.org -ZJGUZL Lunch - Day 1 en en 20260922T120000 20260922T133000 013000 Lunch - Day 1 PUBLIC CONFIRMED Other https://talks.devopsdays.org/dodroxrox26/talk/ZJGUZL/ Main Stage PUBLISH KZLNKA@@talks.devopsdays.org -KZLNKA What We Learned Standardizing Kubernetes Across 4 Clouds en en 20260922T133000 20260922T140000 003000 What We Learned Standardizing Kubernetes Across 4 Clouds PUBLIC CONFIRMED Talk https://talks.devopsdays.org/dodroxrox26/talk/KZLNKA/ Main Stage Marcello Ozzetti Fernando Carvalho PUBLISH HKGHAN@@talks.devopsdays.org -HKGHAN AI Made Developers 25% More Productive. It Also Tripled Our Incident Rate. en en 20260922T140000 20260922T143000 003000 AI Made Developers 25% More Productive. It Also Tripled Our Incident Rate. PUBLIC CONFIRMED Talk https://talks.devopsdays.org/dodroxrox26/talk/HKGHAN/ Main Stage Sylvain Kalache PUBLISH FYYFQA@@talks.devopsdays.org -FYYFQA Snack Break - Day 1 en en 20260922T150000 20260922T153000 003000 Snack Break - Day 1 PUBLIC CONFIRMED Break https://talks.devopsdays.org/dodroxrox26/talk/FYYFQA/ Main Stage PUBLISH QVQYAZ@@talks.devopsdays.org -QVQYAZ Open Spaces: Pay Talk en en 20260922T153000 20260922T160000 003000 Open Spaces: Pay Talk PUBLIC CONFIRMED Open Spaces https://talks.devopsdays.org/dodroxrox26/talk/QVQYAZ/ Main Stage PUBLISH NNY8ZQ@@talks.devopsdays.org -NNY8ZQ Open Spaces - Day 1 - Session 2 - Stage en en 20260922T160000 20260922T163000 003000 Open Spaces - Day 1 - Session 2 - Stage PUBLIC CONFIRMED Open Spaces https://talks.devopsdays.org/dodroxrox26/talk/NNY8ZQ/ Main Stage PUBLISH 87U8LA@@talks.devopsdays.org -87U8LA Open Spaces - Day 1 - Session 3 - Stage en en 20260922T163000 20260922T170000 003000 Open Spaces - Day 1 - Session 3 - Stage PUBLIC CONFIRMED Open Spaces https://talks.devopsdays.org/dodroxrox26/talk/87U8LA/ Main Stage PUBLISH UCU7JC@@talks.devopsdays.org -UCU7JC Open Spaces - Day 1 - Session 4 - Stage en en 20260922T170000 20260922T173000 003000 Open Spaces - Day 1 - Session 4 - Stage PUBLIC CONFIRMED Open Spaces https://talks.devopsdays.org/dodroxrox26/talk/UCU7JC/ Main Stage PUBLISH FEA9K7@@talks.devopsdays.org -FEA9K7 Happy Hour & Snacks en en 20260922T173000 20260922T200000 023000 Happy Hour & Snacks PUBLIC CONFIRMED Other https://talks.devopsdays.org/dodroxrox26/talk/FEA9K7/ Main Stage PUBLISH XSNVRQ@@talks.devopsdays.org -XSNVRQ Registration, Sponsors, Breakfast - Day 2 en en 20260923T080000 20260923T090000 010000 Registration, Sponsors, Breakfast - Day 2 PUBLIC CONFIRMED Break https://talks.devopsdays.org/dodroxrox26/talk/XSNVRQ/ Main Stage PUBLISH ARPBKK@@talks.devopsdays.org -ARPBKK Systems That Respect Attention: Redesigning Ops for Human Limits en en 20260923T091500 20260923T094500 003000 Systems That Respect Attention: Redesigning Ops for Human Limits **Elevator Pitch:** We've optimized ops infrastructure for speed and scale, but not for human attention. This is a framework—and practical patterns—for redesigning ops tooling around how people actually work. **Problem Statement:** Ops teams are drowning in interrupts. Alert fatigue, context-switching, pagerduty storms, Slack avalanches, runbook sprawl. Every tool we add promises to solve the last tool's problem and creates two new ones. The result: slower incident response, worse decision-making, and burned-out people. This isn't inevitable. It's a design choice. Most ops tooling is built as if humans have unlimited attention. **What This Talk Covers (30 minutes):** 1. **The Attention Crisis in Ops** (5 min) - How context fragmentation happens across incident response, on-call, runbooks, and monitoring - Why it matters: empirical connection to incident response quality, burnout, retention - This is not a people problem; it's a systems problem 2. **A Framework: Pull vs. Push, Ambient vs. Interrupt** (7 min) - Core distinction: systems that push notifications vs. systems you pull information from when you need it - The difference between "something happened and I need to decide now" and "I should be aware of this state" - Context assembly: moving this work from human brains to infrastructure - Decision logging: making patterns visible without requiring real-time attention 3. **Concrete Patterns in Practice** (13 min) - Designing ops surfaces for intentionality (TUI vs. web dashboards) - How to structure incident response around attention budget, not alert volume - Building runbook/context systems that assemble *only what's relevant* - Task/intent-driven ops: structuring on-call around actual work, not notifications - Real examples from building systems that respect these constraints 4. **What You Can Do Monday** (3 min) - Design questions to ask when evaluating new tools or processes - How to audit your current stack for attention respect - One pattern to start with if you're redesigning on-call or incident response **Who Should Attend:** - SREs and on-call engineers (this is your lived experience) - DevOps/platform engineers building internal tools - Tech leads and engineering managers concerned about team burnout - Anyone who's felt like their tools are fighting them instead of helping **Audience Takeaways:** - A vocabulary for talking about attention as a design constraint (like latency or cost) - Concrete patterns for redesigning ops workflows - A framework for evaluating whether a tool (or process, or on-call rotation) respects human limits - Permission to push back on "more monitoring" / "more alerts" as a solution PUBLIC CONFIRMED Talk https://talks.devopsdays.org/dodroxrox26/talk/ARPBKK/ Main Stage Abby Malson PUBLISH SXSXDJ@@talks.devopsdays.org -SXSXDJ Context Engineering: The Next Frontier of Your Relationship with Jarvis en en 20260923T094500 20260923T101500 003000 Context Engineering: The Next Frontier of Your Relationship with Jarvis PUBLIC CONFIRMED Talk https://talks.devopsdays.org/dodroxrox26/talk/SXSXDJ/ Main Stage Rainu Ittycheriah PUBLISH KUUWDH@@talks.devopsdays.org -KUUWDH Coffee Break - Day 2 en en 20260923T101500 20260923T110000 004500 Coffee Break - Day 2 PUBLIC CONFIRMED Break https://talks.devopsdays.org/dodroxrox26/talk/KUUWDH/ Main Stage PUBLISH DFZH3R@@talks.devopsdays.org -DFZH3R A recipe : blending the DevOps Infinite Loop and the new ITIL diamond tiles en en 20260923T110000 20260923T110500 000500 A recipe : blending the DevOps Infinite Loop and the new ITIL diamond tiles Too Many Cooks? Blending DevOps and ITIL version 5 Without Burning the Kitchen Blindly implementing both DevOps and ITIL usually leads to conflicting processes and frustrated teams. It doesn't have to be that way. Drawing from real-world banking transformations, this Ignite talk serves up a step-by-step "recipe" to seamlessly integrate DevOps pipelines with the new AI-native ITIL version 5. In 20 auto-advancing slides, you'll learn how to combine both framework through real world experience and step by step approaches mixing CI/CD pipeline and lighter change management, enabling feedback loop with monitoring and observability and more. PUBLIC CONFIRMED Ignite https://talks.devopsdays.org/dodroxrox26/talk/DFZH3R/ Main Stage Catherine Bordinat PUBLISH BZZTJ8@@talks.devopsdays.org -BZZTJ8 our terraform plan output is lying to you (by omission) en en 20260923T110500 20260923T111000 000500 our terraform plan output is lying to you (by omission) PUBLIC CONFIRMED Ignite https://talks.devopsdays.org/dodroxrox26/talk/BZZTJ8/ Main Stage Sudarshan Bhagvan PUBLISH WK7EER@@talks.devopsdays.org -WK7EER The DevOps Metabolism: How CI/CD is Like the Krebs Cycle en en 20260923T111000 20260923T111500 000500 The DevOps Metabolism: How CI/CD is Like the Krebs Cycle The tools we need to create better CI/CD pipelines are already within us - literally! By breaking down the building blocks to metabolism in the body, I want to show Engineers that biological science and computer science are inherently interconnected. If we can break down pipelines in the same way, we can see how to automate in the same efficient way that all of our bodies already do. PUBLIC CONFIRMED Ignite https://talks.devopsdays.org/dodroxrox26/talk/WK7EER/ Main Stage Sophia Solomon PUBLISH CWCSVS@@talks.devopsdays.org -CWCSVS Context Validation: Doc Testing and the Missing AI infrastructure Layer en en 20260923T111500 20260923T112000 000500 Context Validation: Doc Testing and the Missing AI infrastructure Layer PUBLIC CONFIRMED Ignite https://talks.devopsdays.org/dodroxrox26/talk/CWCSVS/ Main Stage Omari Gaskins Jr PUBLISH DBHC79@@talks.devopsdays.org -DBHC79 Lashed to the Mast: A Platform Engineer's Odyssey en en 20260923T112000 20260923T112500 000500 Lashed to the Mast: A Platform Engineer's Odyssey PUBLIC CONFIRMED Ignite https://talks.devopsdays.org/dodroxrox26/talk/DBHC79/ Main Stage Luke Philips PUBLISH 3CDUSJ@@talks.devopsdays.org -3CDUSJ From Practice to Profession: DevOps in the AI-Native Era en en 20260923T113000 20260923T120000 003000 From Practice to Profession: DevOps in the AI-Native Era DevOps did not begin as a profession. It began as a practical response to a painful problem. Development and operations were separated. Releases were slow. Production was fragile. Security arrived late. Feedback arrived later. Teams worked hard, but the system of work made reliable change unnecessarily difficult. DevOps changed that. It gave the industry a better way to think about flow, collaboration, automation, feedback, reliability, security, and continuous improvement. What started as a grassroots movement has now become an enterprise capability. The next step is even more important. DevOps must now mature into a profession. That need has become urgent because AI is changing the speed, scale, and risk of software delivery. AI-assisted engineering can generate code, tests, configurations, documentation, operational summaries, and deployment recommendations faster than traditional delivery systems were designed to absorb. The problem is no longer whether teams can move faster. The problem is whether organizations can validate, secure, govern, release, observe, and improve that work with enough discipline to produce trustworthy outcomes. In the AI-native era, immature DevOps becomes a risk multiplier. Tools alone will not solve this. Pipelines alone will not solve this. Cloud platforms alone will not solve this. AI assistants alone will not solve this. Organizations need a mature DevOps operating model that integrates people, practices, platforms, automation, governance, measurement, and continuous learning. They need internal developer platforms that reduce cognitive load while embedding guardrails. They need pipelines that integrate both human-generated and AI-generated artifacts into a unified flow of validation. They need continuous testing, continuous security, observability, provenance, audit trails, risk-based deployment decisions, and feedback loops that connect production learning back into engineering decisions. This talk will introduce the forward-looking vision for DevOps as a modern profession, as an organization-wide system for value delivery and positions AI-native DevOps as the next stage of professional maturity. The talk will emphasize the need for shared language, standards without rigidity, learning paths, platform engineering, embedded governance, pipeline integration, value stream management, and DevOps maturity assessment. The message is simple: DevOps is not becoming less important because of AI. DevOps is becoming more important because of AI. As AI increases the speed and volume of change, the profession must raise the standard for validation, governance, reliability, security, observability, and accountability. The future belongs to organizations that can combine AI-native engineering with mature DevOps discipline. Attendees will learn: - Why AI-native software delivery requires mature DevOps, not less DevOps. - How platform engineering becomes a scaling layer for enterprise DevOps. - Why pipelines must evolve to validate both human and AI-generated work. - How DevOps connects Agile, DevSecOps, SRE, platform engineering, governance, and value stream management into one operating system for value delivery. - Why DevOps needs shared language, assessment models, learning paths, and professional standards. - The DEVOPS INSTITUTE® Official DevOps book which can be used as a vendor-neutral reference for leaders, practitioners, coaches, assessors, and educators for building mature, AI-ready DevOps capability. DevOps began as a movement. It became a practice. Now, in the AI-native era, it must become a profession. PUBLIC CONFIRMED Talk https://talks.devopsdays.org/dodroxrox26/talk/3CDUSJ/ Main Stage Marc Hornbeek PUBLISH FUHGH8@@talks.devopsdays.org -FUHGH8 Lunch - Day 2 en en 20260923T120000 20260923T131500 011500 Lunch - Day 2 PUBLIC CONFIRMED Other https://talks.devopsdays.org/dodroxrox26/talk/FUHGH8/ Main Stage PUBLISH HMEDVS@@talks.devopsdays.org -HMEDVS Scaling Engineering Teams across Continents en en 20260923T134500 20260923T141500 003000 Scaling Engineering Teams across Continents A review of the lessons learned in building and managing a technical organization of 30 developers arranged into 4 feature teams, operating across two continents (Europe and Asia), two time zones (GMT+2, GMT+7), and representing 9 different nationalities. PUBLIC CONFIRMED Talk https://talks.devopsdays.org/dodroxrox26/talk/HMEDVS/ Main Stage Ludovic Toison PUBLISH RYBRAY@@talks.devopsdays.org -RYBRAY Snack Break - Day 2 en en 20260923T143000 20260923T150000 003000 Snack Break - Day 2 PUBLIC CONFIRMED Break https://talks.devopsdays.org/dodroxrox26/talk/RYBRAY/ Main Stage PUBLISH CQWAED@@talks.devopsdays.org -CQWAED Open Spaces - Day 2 - Session 1 - Stage en en 20260923T150000 20260923T153000 003000 Open Spaces - Day 2 - Session 1 - Stage PUBLIC CONFIRMED Open Spaces https://talks.devopsdays.org/dodroxrox26/talk/CQWAED/ Main Stage PUBLISH CSWHBN@@talks.devopsdays.org -CSWHBN Open Spaces - Day 2 - Session 2 - Stage en en 20260923T153000 20260923T160000 003000 Open Spaces - Day 2 - Session 2 - Stage PUBLIC CONFIRMED Open Spaces https://talks.devopsdays.org/dodroxrox26/talk/CSWHBN/ Main Stage PUBLISH LAAJVL@@talks.devopsdays.org -LAAJVL Open Spaces - Day 2 - Session 3 - Stage en en 20260923T160000 20260923T163000 003000 Open Spaces - Day 2 - Session 3 - Stage PUBLIC CONFIRMED Open Spaces https://talks.devopsdays.org/dodroxrox26/talk/LAAJVL/ Main Stage