A
You are responsible for QA on a complex engineering product and need a clear, repeatable way to handle defects from discovery through closure. Different teams care about bugs differently: engineering wants actionable detail, program leadership wants visibility into risk, and operations wants confidence that fixes are verified before release.
How do you categorize, document, and track bugs to resolution?
