Bugs are defined as flaws that cause unexpected behavior, but not all of them are equally important to fix.
A physical shopping cart with different flaws illustrates how the context and user's goal determine a bug's actual severity.
The START system from medicine provides a color-coded framework for rapidly categorizing bugs based on urgency.
Bug risk can be calculated as the probability of occurrence multiplied by its severity, which includes user count, impact, and duration.
The key factors for assessing a bug's severity are its likelihood, the number of users affected, and its ultimate impact on revenue.
The total time a bug exists is determined by the time to notice it (monitoring) and the time to recover (workflows), which are key DORA metrics.
A strict zero bug policy can lead to over-prioritizing minor issues and prevent teams from working on high-value features.
Instead of a blanket policy, teams should create a clear, shared definition of what constitutes an important problem to guide prioritization.
The discussion covers adapting bug triage for safety-critical platforms, measuring user impact, and handling customer disagreements on bug priority.
27:54Lars Hupel
27:27Christian Seifert
31:54François Martin
08:02Nishil Patel
20:33Nadeen Hussein
28:12Luise Freese
21:39Johannes Hansen
50:10Aicha Laafia
.png?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
Think-cell
Foster City, United States of America
WeMatch GmbH
andrena objects ag