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.
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:
High Severity - High Priority
Low Severity - High Priority
High Severity - Low Priority
Low Severity - Low Priority
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...
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.
Keep reading: What is the difference between severity and priority? and Zero-Bug Policy. If you want to go deeper, I recommend the course Introduction to software testing.