Responding to Incidents

deliver:Agile Live!

| A Virtual Event Series |

Thursday, Apr 22 — Online

 09:00am PT | 12:00pm ET | 6:00pm CET

$20 Agile Alliance Member Rate
$30 Non-Member Rate
included in $99 deliver:Agile Live! annual pass

For many people, the first day back to work in 2021 was a pretty light day. Why? Because Slack, the chat app used by a huge number of organizations, had a major outage on January 4th. Immediately social media lit up not just with folks wondering what was happening but also folks tweeting with the #hugops, a hashtag that acknowledges the human side of software incidents.

As Agilists, we focus on frequently delivering working software, but in complex technical ecosystems, software and systems can interact in unexpected ways that impact users. In this session, Cat Swetel will be joined by a panel of incident experts.


Courtney Nash

Courtney Nash
Incident Librarian at Verica

View Bio

Coming Soon


Gregory Vigneaux
Co-founder of the Adapt Institute

View Bio

Gregory Vigneaux is a former wildland firefighter for the National Park Service and U.S. Forest Service now researching the management of incidents from the perspective of design, philosophy, and complexity. He holds an MS in Emergency Management, has cofounded the Adapt Institute, and worked for FEMA and Save the Children.

Nora Jones

Nora Jones
Founder & CEO at

View Bio

Nora is the co-founder and CEO of Jeli. She is a dedicated and driven technology leader and software engineer with a passion for the intersection between how people and software work in practice in distributed systems. In November 2017 she keynoted at AWS re:Invent to share her experiences helping organizations large and small reach crucial availability with an audience of ~40,000 people, helping kick off the Chaos Engineering movement we see today. She created and founded the movement to develop and open-source cross-organization learnings and analysis from reliability incidents across various organizations, and the business impacts of doing so.

We will explore the entire lifecycle of an incident:

  • How do systems drift into failure?
  • What are effective and ineffective ways of facilitating incident response?
  • What is the best way to learn from incidents after they have occurred?
  • How can we be transparent with users and maintain or restore trust after an incident?

Why You Should Come

Over the past few months, the community of technical Agile practitioners has been buzzing, wondering what does it mean to deliver working software in complex technical ecosystems that are constantly changing. Yes, we can deliver software that works, but how do we keep software working? In a world where failure is inevitable, how do we ensure we learn from incidents and avoid the stress and unhappiness that comes from constantly living right at the safety margin?


If you are not yet an Agile Alliance Member, you can become one here.