Product Delivery

The product has undergone several unexpected changes during your previous test cycles and as a result there have been more test cycles than originally planned. Marketing has a firm deadline on which to announce this product to the public and upper management feels obligated to deliver on schedule. Nevertheless, your test team had discovered several priority 1 defects in the last test run and the product is nowhere near meeting the company's exit criteria. As a test manager, how do you handle this situation?

Questions by kurtz182   answers by kurtz182

Showing Answers 1 - 3 of 3 Answers

virgosls

  • Aug 14th, 2010
 

As requirement is frequently changing then the extra efforts to incorporate these changes must be published by Test manager to all the relevant parties and release must be postponed.

But If release date can't be postponed, then in that case,

1. Find out defect density of different components. E.g. there 15 components in new release out which 70 to 80% problems from 2 components. These components can be taken away from release and published in next sub release shortly with valid fixes.

2. Testing efforts should be more focused on flows which are most commonly used by end customers.

3. Testing should be carried out in spiral model. e.g. Top 10 execute testcases against for P1 defects then move to next defect so that end of every day only 1-2 defects are not regressed but almost every defect is touched and tested at high level. If we found any discrepency then same should be notified to dev team immediatly.

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