Agile Book Club: Incident Analysis

Despite your best efforts, your software will sometimes fail to work as it should. Some failures will be minor; others will be more significant. Either way, once the dust has settled, you need to figure out what happened and how you can improve. This is incident analysis.

📖 Incident Analysis

🎙 Discussion prompts:

  • Think of an incident or bug you were involved with. What happened? Share the story.

  • When you look back at that incident/bug, what were some of its causes?

  • What aspects of your development system contributed to the incident or bug? Which aspects made it less harmful?

  • How could your development system be improved to make incidents and bugs less likely in the future?

About the Book Club

From October 2021 to August 2022, I hosted a call-in talk show based on the second edition of The Art of Agile Development. The series used the book as a jumping-off point for wide-ranging discussions about Agile ideas and practices, and had a star-studded guest list.

For an archive of past sessions, visit the book club index. For more about the book, visit the Art of Agile Development home page.

If you liked this entry, check out my best writing and presentations, and consider subscribing to updates by email or RSS.