language agnostic - How to prioritize bugs? -
Between the testing and development teams, my current company does not have a clear understanding of how serious the bug should be. There are arguments that move forward and backward to reduce or increase the severity. We now know about the rules that add to the rules. The tester raises the bug and provides priority based on his intuition. The developer will request a change based on their load or some other factor.
How is the severity of the bug / priority classified? Is there any criterion that guides how the priorities of software defects are determined based on customer's needs, time limits and other things?
priority level , which deliberately < Em> Do not have anything to do with severity or effect , and just describe the conceptual situation of the bug in the schedule. This area will determine which bugs work, so it should be very clear that the bug fact is not open to the conversation.
Use the severity level , which are deliberately valid, validated definitions, with determining or prioritizing Nothing to do, I've done generalized work to successfully implement programming projects in general.
Then by negotiation or whatever, severity is free without affecting the factual information in the area.
Trying to face both "seriousness" and "priority" "In a single field, soul-plurality logic and waste time can be used to determine the bug reporter For how a "bad" bug is, a firm guide to fact is required, and it is necessary to accept it easily by independent parties. On the other hand, the right goal for priority, negotiation and scheduling is the goal.
Comments
Post a Comment