Defect severity and priority

Severity of a defect indicates how serious its impact on the system is, while priority indicates how urgently it needs to be fixed based on business needs. Severity is usually assigned by the tester, and priority by the lead or the product owner.

Is the severity the same as the priority? What are your differences? In this video I'd like to talk about this, but if you want, I summarize a little: 

the severity is related to the impact that a defect has to occur while the priority is given by the business and is related to the urgency of resolution. In addition, the severity is usually assigned by the tester, while the priority is usually assigned by the leader or the product owner. Finally, the severity of a defect, in general, does not change throughout the life cycle of that defect. However, the priority can change because it depends on multiple factors, including severity, but it is not the only one.

Differences between severity and priority

SeverityPriority
What it measuresThe impact of the defect on the system or the userHow urgently it needs to be fixed
Point of viewTechnical / functionalBusiness
Who assigns itUsually the testerUsually the lead or the product owner
Does it change over time?Generally not; it stays the same throughout the defect life cycleYes, it can change depending on the context (dates, clients, releases)
What it depends onHow much it affects the system behaviorSeveral factors, including severity

The question then arises ... What is the relationship between severity and priority? If the severity is high, the priority has to be high? Not necessarily, in the video I'll tell you some examples of the 4 combinations:

CombinationExample
High Severity - High PriorityThe pay button of an online store does not work and nobody can complete a purchase.
Low Severity - High PriorityThe company logo or name is misspelled on the home page.
High Severity - Low PriorityThe application crashes when generating a report that only one client uses once a year.
Low Severity - Low PriorityA typo on a help screen that almost nobody visits.

Finally, remember that the values assigned to priority and severity depend on each project and that it is good that all the team has them clear to avoid misunderstandings.

I recorded the video from Mar del Plata (Buenos Aires, Argentina). We went there with Gustavo Terrerato present Argentesting to the offices of ATICMA. 

Spanish version

English version

Courses that might interest you...

SAVE
58.18%
4 - course bundle

Starter Bundle

14

Severity and priority in a job interview

The difference between severity and priority is one of the most common questions in tester job interviews. In this video I share a possible answer:

Frequently asked questions

What is the difference between severity and priority?

Severity is about the impact of the defect; priority comes from the business and relates to how urgently it must be fixed.

Who assigns each one?

Severity is usually assigned by the tester; priority by the lead or product owner. Severity usually doesn't change, while priority can.

If the severity is high, does the priority also have to be high?

Not necessarily. A serious defect in a feature that is barely used can have low priority, and a minor but very visible defect can have high priority.

What severity and priority levels are used?

It depends on each project and tool. For severity it is common to use critical, high, medium and low; for priority, high, medium and low or a 1 to 5 scale. The important thing is that the whole team is clear on the criteria.

How do I answer this question in an interview?

Explain what each one measures, who usually assigns it, and give an example of a combination, such as a typo in the logo on the home page: low severity, but high priority.

Keep reading: Because we don’t just report bugs and Zero-Bug Policy. If you want to go deeper, I recommend the course Introduction to software testing.