Videos

How are you doing with service reliability? How well are teams responding to and resolving incidents? What are your MTTx metrics and how efficient is your process?

Service level objectives (SLOs) define what “success” means for engineering orgs, based on the user experience. It’s a whole new way of understanding your production services that helps keep customers satisfied and boosts development velocity. Another benefit to using SLOs is being able to align multiple teams on shared goals — from product to dev, ops, sales, and so on.

A retrospective (or post-mortem) is a critical part of Incident Response. If you don’t document, share, and learn, everyone misses out on a critical learning opportunity. Retrospectives are designed to help teams collectively learn, iterate, and improve. It involves taking the time to story-tell exactly how an incident took place and discussing how to do better next time. The key is to shine new light on processes, tools, and systems so that you know how to fine-tune.

Every field of endeavor has its leading edge where the answers are unclear and active exploration is warranted. Although the phrase "here be dragons" might be an appropriate warning, this panel of intrepid adventurers will venture into that unknown territory.

What can we learn about working through and analyzing IT incidents from the high tempo, very high consequence world of medical emergency rooms? What does vulnerability have to do with psychological safety, creativity, and team collaboration? It turns out that we can learn quite a lot. We can all benefit from drawing connections across different fields of study and this panel will explore some of these connections. DevOps Enterprise Summit Virtual - US 2021

On call doesn’t have to suck. Right? Some vendors even have this as a tagline. Truth is some on-calls do suck (a little) especially if it’s a Sev0. Ever been in a chaotic on-call environment? Unclear on who’s doing what and how to run the playbook. Is there a playbook? This session shares approaches that simply work and more importantly how teams learn and improve over time. From living through inevitable incidents and reviewing retrospectives, everyone up-levels and learns. Happier DevOps teams, happier customers. Presented by Paul Chu, Head of Customer Success at Blameless.

The networked software systems we build are increasing in complexity every moment. Today the most successful builders and operators are embracing complexity through CI/CD, Chaos Engineering, and innovation in Incident Response. They realize that the adaptive world around us is advancing at such a breakneck speed, it is leaving our capacity to understand it in the dust. That humans and technology must race a gauntlet of automation surprises and collaboration challenges as a team, learning and improving along the way. This session showcases methods of deploying, running, and navigating complexity. It offers a practical view of how software systems can scale and remain robust to failure (like fallbacks or high availability), achieve highly reliable socio-technical operations (via runbooks and game days), and adapt to surprise through techniques of resilience engineering (graceful extensibility and building for adaptation).

Reaching higher levels of the organization is essential to achieving broader adoption of SRE. Without the right buy-in even if parts of SRE are rolled out, behaviors will regress. How then do you get this support? It starts with finding out the incentives needed by key levels of leadership and how to effectively speak to those. It also requires listening to the resistance to SRE adoption, and then effectively address that resistance with reason and metrics. In this talk, I share how to persuade the right level of leadership so that an organization can progress the adoption of SRE through key stages. I provide case studies of how real companies have succeeded or failed with their SRE adoption. This talk aims to equip the audience with the tools to promote SRE adoption through a grassroots/bottoms-up approach.