Defect management, triage, severity and backlog hygiene

Defect management and backlog hygiene

A defect is a request for someone’s time. It gets that time when it says who is affected, what they could not do and what happens if it ships. It gets ignored when it reads like a matter of taste.

These notes cover the whole life of a defect: how it is written, how triage decides, how severity is argued, and how a backlog is kept small enough that the important tickets stay visible.

2 notes on defects and backlog

P219 Aug 20267 min read
Defects Product thanks you for (and ones they ignore)
Not every bug earns attention. How I write defect reports that name the user impact, the business risk and the next action, and how I tell when a finding is not a defect at all.
P012 Aug 20267 min read
Defect backlog hygiene beats writing more cases
Stale bugs drain more engineering time than missing coverage. How I sweep a defect backlog, close what is dead with a reason and leave a board Product and Engineering both believe.

2 notes on defects and backlog

Defects Product thanks you for (and ones they ignore)

Defect backlog hygiene beats writing more cases