Which of these is the most important one to fix first, and why?
a. The word "BlackBerry" is misspelled on the startup screen of the application. b. The application always rejects a user's first attempt to launch the application; subsequent attempts are successful. c. The application crashes and brings down the database server when it tries to add a record that contains an uncommon string, "123abc456xyz789".
Total Answers and Comments: 15
Last Update: November 06, 2009 Asked by: oranger34
The third bug that is pulling down the database server is the most important to fix, the second bug that the application does not start in first go should be fixed next. Then the bug regarding the spellings should be fixed.
The bug that is pulling down the server, is most important because server is also being used for other transactions of the same application. The server is being used to for other applications as well. Pulling down of the server means deadlocking of so many applications. Even though Blackberry is mis-spelled, it is still understandable. However, if the application is not logging in on first attempt, the application is causing waste of effort on every time of logging leading to loss of time everytime the application is logged in for further testing.
The third bug that is pulling down the database server is the most important to fix the second bug that the application does not start in first go should be fixed next. Then the bug regarding the spellings should be fixed.
The bug that is pulling down the server is most important because server is also being used for other transactions of the same application. The server is being used to for other applications as well. Pulling down of the server means deadlocking of so many applications. Even though Blackberry is mis-spelled it is still understandable. However if the application is not logging in on first attempt the application is causing waste of effort on every time of logging leading to loss of time everytime the application is logged in for further testing.
The third sceanario rarely happens so it should be lower priority though it is estimated as higher severity. The second defect could annoy the end users severely while the first one maybe obvious and impact user experience. My personal opinion is c>b>a
Priority will be given based on stage of life cycle
1) Assume that application is middle stage (I mean to say build is 3rd one and still few more to come) and you are testing the application to accept it (Smoke/sanity Testing) for further testing I would like to give the preference as B A C Why I am giving last preference to C is when I am giving uncommon string then the application is getting crash but as of now we have alternative and that is positive value so with positive value we can work with the application Next why A is given second preference black berry Its company Name not a simple title of application
And lastly why I am giving first preference to BI am not able to launch the application in first attempt then it is a major issue while accepting the build (smoke/sanity testing) if you are not able to launch then definitely we will reject the build.
2) Assume application is completed and ready for use then also I will give B A C Let me tell you in general way Suppose you are a customer and interested to purchase Blackberry mobile and if it is not launching in first attempt do you purchase that piece no one will purchase and coming second one company Label Company goodwill is linked to it and with this mistakes goodwill will be degraded so second preference and coming to last one we have an alternative and that is we can give positive values with which that particular functionality will work Please correct me if I am wrong.
First Priortize to Functional Bugs B it shows the Database error on adding a Record. This is a common functions that to used in the Application. So this should be fix first.
Second Priortize to Installation A No customers will not be adjust on launching errors in the application so it should be fix next.
Last Priortize to the Missspelled bugs C. Products are identifies through by the name. so it should be next.
Defect priority is how much impact the defect will impose on business.
According to me the order is: B: No user loves being nagged to enter the same information N times that too before getting authenticated to an application. So this stands to be at priority 1.
A: If the word is misspelt on the start up screen itself then the business reputation will be questionable. Believe me clients make major issue of such cosmetic issues. This ranks at 2 compared to B.
C: The application crashes on entering a rare/uncommon entry. This is a high severity issue but low on priority. This fix can be deferred.
C is critical and blocking issues it will block large number of test cases too and has high impact on the business so this needs to be fixed very urgently
B is High priority bug and also needs to be fixed immediately
A is medium priority bug and needs to be fixed on need based.
1 
2