Finding a defect is only the beginning. Defect management is the process of recording, triaging, fixing, verifying, and closing defects in a controlled way so nothing slips through the cracks.
The defect lifecycle
A typical defect lifecycle
New
→
Assigned
→
Open / In progress
→
Fixed
→
Retest
→
Closed
A defect may also be rejected (not a genuine bug), deferred (fixed later), or reopened if a fix fails retesting.
Anatomy of a good defect report
- Clear title — a one-line summary of the problem.
- Steps to reproduce — exact, numbered steps.
- Expected vs actual — what should happen and what did.
- Severity and priority — impact and urgency.
- Evidence — screenshots, logs, environment, build.
Severity vs priority: severity is how bad the defect is; priority is how soon it should be fixed. A minor typo on the home page can be low severity but high priority.
Conclusion
Defect management ensures every issue is tracked from discovery to resolution. A clear lifecycle and well-written reports mean defects get fixed faster, verified properly, and never quietly lost.