You have completed a project and the live date is nextday, you got one big problem but that problem can't be resolved in short time and the estimate is 30 days. Waht are your options ..?

  • Interview Candidate
  • 21
  • 2578

Showing Answers 1 - 21 of 21 Answers

Chitra

  • Mar 1st, 2006
 


We could think of any workaround which would be suitable at that point of time for the problem, and make  a note in the Release notes.

In case there is no workaround, then a note should be mentioned in the release notes stating it as a known issue.

Thanks

Chitra

ashwini

  • Mar 3rd, 2006
 

if u elimanate that part does it wont affect the other part in the application

  Was this answer useful?  Yes

Jayanthi

  • Mar 3rd, 2006
 

if it is a Product Based Application i.e. no client, then simply eliminate the feature which is causing problem and can launch the product.

if it is a client based product, here also can eliminate the feature which is causing the problem, but with the prior permission from the client.

  Was this answer useful?  Yes

Bindu05

  • Mar 30th, 2006
 

1.Evalute the risk because of this bug

2.Try to find the workaround to fix this bug

3.Disable this particular feature and go live with other functionalities if this feature doesnot impact on other functionality.

4.Also check the acceptance criteria for the product .Sometimes the client may say  1 critical bug is ok but not 2 or more  ?.

  Was this answer useful?  Yes

Praveen.

  • Apr 5th, 2006
 

Hima, you are right.

Compliment to that,

Mention it in the release notes.

Release your product.

After that fix it and comeup with a patch(fix) immediately.

  Was this answer useful?  Yes

urmilashiv

  • Aug 4th, 2008
 

If all the processes (unit testing, component testing, system testing etc) were followed correctly then this problem whose fixing/retesting  estimation is 30 days should not have come at all.

If at all such issue has come, then call an urgent meeting with the client, test engineers, developers. Look for a work around. If there is nothing, take the permission of the client and drop that feature and mention in the release note as a known issue.

  Was this answer useful?  Yes

vk1978

  • Apr 18th, 2009
 

In real time defect's can be found at any point of time, but defects that takes 30 days to resolve then no client will accept the it, because definately such defects impact will more on the application. 


So, Project Manager should convenience the client and release the product/application with known issues and fix the defect ASAP and release the patch and make sure that is working fine

Or else release date should be extended to 10 or 15 days and by taking client's acceptance and fix the defect ASAP by making use of more resources  and then release the product/application.

please correct me if i am wrong

  Was this answer useful?  Yes

srinivasulub1981

  • Nov 26th, 2009
 

Hi

As a tester we can find out the issues at any time as no one can give 100% bug free product, but the thing is we must find out the major issues while doing regression testing, alpha or beta testing it self.

  If at all found the issues in above said situation, first of all need to intimate to client ( through our TL or PM) and need to explain with proper reasons why that was missed in our testing, try to convience him, i feel no client will accept the application with major issues, so altimately he can give the time.


CNU

  Was this answer useful?  Yes

kurtz182

  • Dec 10th, 2009
 

Our options depend on the company profitability and customer perception.
   

Options:

1) If the functionality is not mission-critical, then release the application with the impaired functionality. Inform customers that this is a known defect.

2) Create a workaround (a patch) that will fix the problem in the short term.  This option sounds good on paper.  Yet this is feasible only if the patch can be furnished in a short period of time.  If it takes two weeks to produce a workaround, then it may be better to postpone the release for 30 days and place all of our development effort toward permanently fixing the impaired functionality.

3) Simply postpone the release of the product until the broken functionality is fixed. Maybe our business can live without this product over the next 30 days and a development effort to produce a workaround would not be cost-effective.

4) Remove the problematic functionality and release the product. Probably the least likely option. Yet this may be feasible if it is not a mission-critical functionality, if other functionalities do not depend on it and if this option can be accomplished quickly.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions