Anja Kunkel

How to ignore bugs (safely)

Is your 'Zero Bug policy' actually slowing you down? Learn a data-driven triage system to focus your team on the bugs that truly matter.

How to ignore bugs (safely)
#1about 1 minute

Defining bugs and the need for effective triage

Bugs are defined as flaws that cause unexpected behavior, but not all of them are equally important to fix.

#2about 3 minutes

Using a shopping cart analogy for bug severity

A physical shopping cart with different flaws illustrates how the context and user's goal determine a bug's actual severity.

#3about 3 minutes

Applying medical triage principles to software bugs

The START system from medicine provides a color-coded framework for rapidly categorizing bugs based on urgency.

#4about 3 minutes

A formula for calculating bug risk and severity

Bug risk can be calculated as the probability of occurrence multiplied by its severity, which includes user count, impact, and duration.

#5about 2 minutes

Breaking down risk: probability, users, and revenue impact

The key factors for assessing a bug's severity are its likelihood, the number of users affected, and its ultimate impact on revenue.

#6about 3 minutes

The role of time to notice and recover (DORA metrics)

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.

#7about 4 minutes

Why a zero bug policy can be counterproductive

A strict zero bug policy can lead to over-prioritizing minor issues and prevent teams from working on high-value features.

#8about 1 minute

Defining what makes a bug important to your team

Instead of a blanket policy, teams should create a clear, shared definition of what constitutes an important problem to guide prioritization.

#9about 2 minutes

Q&A on safety-critical systems and customer feedback

The discussion covers adapting bug triage for safety-critical platforms, measuring user impact, and handling customer disagreements on bug priority.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

Related Articles

View all articles
JC
Jordan Cutler
A Guide to Public Speaking For Software Engineers
“Your technical skills are where they need to be, but you need to improve your communication.” - Your manager. This is one of the hardest pieces of feedback to hear as a software engineer. Why? Because you probably thought as a software engineer you ...
A Guide to Public Speaking For Software Engineers
DC
Daniel Cranney
Dev Digest 188: CfP time, the risks of NPM and IKEA algorithms
Inside last week’s Dev Digest 188 . 🤖 GitHub Copilot CLI is now in public review 💻 Microsoft is bringing ‘vibe working’ to office apps 🎣 Attackers abuse AI tools to generate captchas in fishing attacks ⚠️ When LLMs autonomously attack 🧠 Common cause...
Dev Digest 188: CfP time, the risks of NPM and IKEA algorithms

From learning to earning

Jobs that call for the skills explored in this talk.

Rust and GoLang

Rust and GoLang

NHe4a GmbH
Karlsruhe, Germany

Remote
55-65K
Intermediate
Senior
Go
Rust