Ship Fast x Fix Fast: The Full DevOps Picture with CircleCI and PagerDuty

A joint online webinar from CircleCI and PagerDuty. The subject is the failure mode every team hits once deploy frequency goes up: more releases means more change-induced incidents. The talks cover how to shorten the gap between noticing a problem and fixing it, and how to stop the same incident from happening twice. The framing is that DevOps only completes its loop when feedback runs both ways, development to operations and operations back to development. Session 1 draws on the State of Software Delivery data report published in Q2 2026 to show where time and cost accumulate in a pipeline. Teams shipping comparable volumes of change can have very different CI/CD cost structures, and the session compares top-performing teams with median teams to explain where that gap comes from, using the report's model cases as a starting point. Session 2 covers the first minutes of an incident: who notices, who gets paged, and what they look at to make a call. Teams without an answer to that often spend longer assembling people than finding the cause. Beyond alerting and escalation design, the session looks at treating post-incident review as an input rather than a document, feeding the weak points it surfaces back into the next round of fixes and tests. It is aimed at development teams struggling with CI/CD run time and cost, teams whose incident response starts with hunting for an owner, and SRE or platform teams that want MTTR and change failure rate watched on the development side too. Runs 12:00 to 13:00, free to attend, with a Q&A segment.