Quality is delighting customers
The bugs should be logged and approved as soon as possible and it should be tracked with different stages.. An effective bug management tool will help in this like Quality center, bugzilla etc.
And if there is no tool then we should have manage them with different excels sheet prepared in the formats matching some tools.
Defect tracking management is crucial for quality assurance and certification. It is matter of belief for team, management as well as customer that whatever defects surfaced are prioritised and resolved in releasing version.
It is possible with quality passionate test manager who can setup centralised repository and conduct meetings before releasing product/application to customer. Pre-release Meeting updates all the concern people what are things done on latest version and can avoid last minute surprises. I always recommend to inform customer before releasing what are the known defects in the upcoming version and with permission that can be resolved in next version to meet present deadline of delivery. If customer understands severity of defects and realises delivery date can be differed for best quality then you would fix them and release it.
I welcome comments.
Business and Software Architect
I could list you many reasons, but will shorten my list to a few important ones:
1. Gives you and the stakeholders a vision on the quality of the code
2. Enhances confidence in testing by exposing flaws in the behavior
3. Helps you in your quest of measuring the gating criteria's for exiting test phases
4. Keeps an audit trail of the number of defects logged for a project/program of x complexity and y size. (This info can be used as a benchmark to further provide testing timelines and estimations on similar projects/programs in the future)
5. Exposes requirement gaps and possible change requests.
G.N.Mallikarjuna Rao stated it excellently with pre-release meetings and customer focused fixes.
With effective bug management there is also a need of mapping to test cases. Every failed test case should have a bug report against it with the severity understood. The more test cases that fail with one bug mapped helps identify retest time and priority. Once its fixed the team will already have an understanding retest time required/planned which will help expedite the release.
Collective bug management can also expose regression retest needs.
As per functional testing services