10 Critical Elements of a Bug:
Day #5
Go To: Day 1 - Day 2 - Day 3 - Day 4 - Day 5 - Day 6 - Day 7The Priority field is best owned by the Producer or Project Manger. The Priority determines how important the bug is to fix. The most common designation for this field is Priority “X” where X= a number. Priority 1 (P1), Priority 2 (P2), etc.
Element #8:
Priority
QA should not set the Priority of a bug – ever! That being said, each company does things a little bit differently and you may work for a company that wants QA to set the Priority of the bugs that it enters.This is a mistake, but plenty of companies make it. If you are called upon to set the Priority, get CLEAR definitions of each Priority from your QA Lead or Manager before you begin using this field – and then be sure to follow those definitions as best you can. Once entered and reviewed, each bug is given a Priority designation. This represents how important the bug is to fix in the current release. Factors taken into consideration when setting Priority are, complexity of the fix, time to implement the fix, risk level of implementing the fix, time needed to test the fix, etc. The Producer or Project Manager or Engineering Lead will set the Priority of bugs as they are reviewed. This helps clarify to the whole team what work is to be done next. Go To: Day 1 - Day 2 - Day 3 - Day 4 - Day 5 - Day 6 - Day 7Return To Successful Quality Assurance Home
|
