Modern QA2026The Two-Axis Matrix — tiles
Log inJoin
47 / 71 · 11 Manual Testing Fundamentals · Severity vs Priority← prev⊞ allnext →☰ Read as one page

6.3The Two-Axis Matrix

High Priority Low Priority
High Severity App crashes on checkout for all users — fix now App crashes when entering 10,000-character name — rare edge case, fix in next sprint
Low Severity CEO's name is misspelled on the homepage — cosmetic but urgent Footer link color is slightly off-brand — fix eventually

Analyzing Each Quadrant

High Severity + High Priority (top-left): The obvious emergencies. Production is down, users are losing data, security is breached. Everyone agrees these get fixed immediately.

High Severity + Low Priority (top-right): Severe bugs that rarely occur. A crash that only happens with a 10,000-character input is technically critical but affects almost nobody. Schedule the fix, but do not interrupt the current sprint.

Low Severity + High Priority (bottom-left): Cosmetic or minor issues with outsized business impact. The CEO's name misspelled on the homepage is a trivial bug, but it needs to be fixed before the board meeting tomorrow. A broken link on a campaign landing page during a marketing push.

Low Severity + Low Priority (bottom-right): The backlog inhabitants. Minor visual issues, edge-case formatting problems, improvement suggestions. These get fixed when there is bandwidth, or during dedicated cleanup sprints.