What is The Difference Between Severity And Priority?
Severity: It is the extent to which the defect can affect the software. In other words it defines the impact that a given defect has on the system.
Priority: Priority defines the order in which we should resolve a defect. Should we fix it now, or can it wait? This priority status is set by the tester to the developer mentioning the time frame to fix the defect. If high priority is mentioned then the developer has to fix it at the earliest. The priority status is set based on the customer requirements.
Examples:
High Priority & High Severity: An error which occurs on the basic functionality of the application and will not allow the user to use the system.
High Severity & Low Priority: An error which occurs on one of the functionality of the application and will not allow the user to use that functionality but that functionality which is rarely used by the end user.
High Priority & Low Severity: The client logo is not appearing on the web site but the site is working fine. in this case the severity is low but the priority is high because from company's reputation it is most important to resolve. After all the reputation wins more clients and projects and hence increases revenue.
Low Priority and Low Severity: Any cosmetic or spelling issues which is within a paragraph or in the report
So the bottom line is that in the priority v/s severity matrix the priority is completely business impact driven and the severity is completely technical impact driven.
Severity: It is the extent to which the defect can affect the software. In other words it defines the impact that a given defect has on the system.
Priority: Priority defines the order in which we should resolve a defect. Should we fix it now, or can it wait? This priority status is set by the tester to the developer mentioning the time frame to fix the defect. If high priority is mentioned then the developer has to fix it at the earliest. The priority status is set based on the customer requirements.
Examples:
High Priority & High Severity: An error which occurs on the basic functionality of the application and will not allow the user to use the system.
High Severity & Low Priority: An error which occurs on one of the functionality of the application and will not allow the user to use that functionality but that functionality which is rarely used by the end user.
High Priority & Low Severity: The client logo is not appearing on the web site but the site is working fine. in this case the severity is low but the priority is high because from company's reputation it is most important to resolve. After all the reputation wins more clients and projects and hence increases revenue.
Low Priority and Low Severity: Any cosmetic or spelling issues which is within a paragraph or in the report
So the bottom line is that in the priority v/s severity matrix the priority is completely business impact driven and the severity is completely technical impact driven.
No comments:
Post a Comment