Defect triage is the recurring process of reviewing reported defects and deciding what to do with each — fix now, fix later, won't fix — based on severity, priority, effort, and risk. Advocating for quality is QA's role in that process: making the case for defects that matter without being obstructive or a zealot.
Triage typically involves QA, the PO, and dev leads reviewing new defects and agreeing on disposition. QA's job is to bring clear, factual information to each defect — accurate severity, real user impact, reproduction steps, affected scope — so decisions are made on evidence, not volume or emotion. Effective quality advocacy is a balancing act: QA must champion important defects (especially data, security, and core-flow issues) and push back when serious problems are being waved through, but must also accept that not every defect can or should be fixed immediately — the business legitimately balances quality against time-to-market and other priorities. The wrong postures are being a 'quality zealot' who insists every trivial bug blocks release (which gets QA ignored) or a pushover who lets serious defects slide silently. The right posture is a credible advocate: you quantify impact, propose reasonable options (fix, defer with a tracked ticket, mitigate with a flag), and escalate clearly when a genuinely unacceptable risk is being accepted. Building this credibility — being right about what matters and pragmatic about what doesn't — is what makes QA's voice carry weight.
In triage, a developer wants to defer a bug where order totals occasionally round wrong by a cent. QA reframes it with facts — it affects financial accuracy, compounds across thousands of orders, and could cause reconciliation and trust issues — which elevates it from 'minor' to a prioritized fix, while QA simultaneously agrees to defer several genuinely cosmetic issues to keep credibility.
DEFECT TRIAGE BOARD — Sprint 34
ID Summary Sev QA-advised action
---- ----------------------------- ---- ------------------------------
#812 Order total rounds wrong 1c High FIX NOW (financial accuracy)
#813 Session not cleared on logout High FIX NOW (security)
#814 Search slow with 10k results Med Defer w/ ticket + perf backlog
#815 Tooltip text truncated on IE Low Won't fix (unsupported browser)
#816 Button 2px misaligned Low Defer (cosmetic backlog)
QA stance: escalate #812/#813 strongly; concede #814-#816 to
stay credible. Advocacy is targeted, not blanket.Scenario: In defect triage, the Product Owner wants to defer almost every bug you've raised to 'protect velocity', including one where users' sessions aren't fully cleared on logout. You feel quality is being sacrificed, but you don't want to be the person who blocks everything. How do you handle it?