What to do when on the eve of the release specifically faced in many bugs �?? how does not process this minimum risk factors?

Context
The development team: 9 QA / testers / enhancement version 1 of a series of Microsoft Dynamics CRM. 2, 3... 0, And 4. 0 Minutes including the maintenance of add-on products for 18 of 21 members.
Release: all upgrades previous versions of the release) via deployment products across multiple environments worldwide release to support multiple languages in English, French, German, Dutch,.
The first release is very busy did. Defects in the release candidate of search for the test team report went to their work. By defects in product management and fixes it, depending on the priority development team. Number of bugs using the overwhelming to many because...... experience the write is threatened. This, despite of all quality assurance activities the following coding, code reviews, unit tests, and official test like the. Something bad had interest in growing it is.
Problem at hand to carefully analyze defects of many system for quite some time since is was direct result of recent developments and improvements are not figured it out. The bug is really didn't ? t ministries ministries users. How to use the system to block this bug didn't ? affecting, or perhaps most. Alternatively, you could probably find a workaround.
In the when a defect free our baseline idea reside on the system. During the following regression cycle we documented flaws were found in the Excel sheet and check these cross with defect was already logged in as project management tools. Wow! is one huge exercises. It's worth.
To classify defects at the end of facilitated information collected in this exercise, we
* To eliminate duplication of our duplicate-were logged many duplicate issue tool. It a number of bugs to reduce, provided as a system cleaning!
* Issue closed-defect was closed on the previous version, was opened again
* Classic problem-found already in the previous versions and defect status (with the lowest priority) to open the
* New problems-seen only in the current regression defects
* Redundant problem-they are irrelevant ? open ?, was supposed to change the current system capabilities and future expected behavior
Duplicate, removes the redundant defects. This is a cleaner tool and defects considerably decrease results! legacy issues in the US is baseline defect sheet and it is listed. It had information such as number of defects, defects in title and version numbers reported. So only was left to deal with the renovation and new defects
When this information becomes available, it is a huge relief anyone care was. Now more manageable numbers looked. It contributes to
* Better prioritization of product management
* The development team to focus on the release on priority defects
* Focus on good system test, test team.
Baseline defect sheet was very important QA artifact;, refers to prepare the future, we are more effort and time to save. Defect relative defect sheet found in the regression was a cross-check. Doesn't the bug log in or already had. This considerable defects, i.e. actually reduced the number of defects were introduced between the open or current Sprint. In all releases, known issues and version number, the priority low baseline sheet has been added. As a whole contributes to the optimal utilization of the available time and labor, decreases the stress level in the team.
Finally release was stabilized very became a non event! we have few published ago release, release was able. Also good relevant?? may have seen it believable! this base lining flaw for full was of course. Other factors were required too. The big things this huge contributing factor is the scheme as it resulted in what is known as a sustainable productivity ? ?

Article source: http://www.BharatBhasha.com
Article URL: http://www.bharatbhasha.com/metaphysical.php/236291

Article added to May 1, 2010
LD

View the original article here