Mahalakshmi

• Jan 15th, 2007

 

There is no named process for Defect Management. Nevertheless the tester needs to track the defect raised by him/her till closure. As a test lead its a vital responsibility to ensure the defect raised is validation by him/her in a triage checking its genuinity & aesthetics. Later the defect needs to assigned to the right contact in development team. Now this defect if accepted by the development will be fixed and released to QA in the next build. Tester should test and close the defect if this defect no longer exists or else re-open the same defect. Sometimes a fix for a defect gives raise to more defect or affect a functionality. A good tester always looks at identifying these flaws also. After each cycle, a lead needs to prepare a metrics depicting the Fall/Rise in the defect count(valid) and rate of defect fix. At end of the testing cycle, a final metrics of this sort shall help the Development & Business get the Stability index of the application.Deriving the Module wise defect report indicating the root cause is the main input for Root Cause analysis meet, in which Pivot table & Fish bones diagrams are drawn to understand the root causes of each defect/class of defects. This helps in executing the next project/release better by implementing the learning from the current project.

rajkumar194

 Profile Answers by rajkumar194 

• Mar 17th, 2007

 

hi,
this is rajkumar.i read about def management,it's very nice.

what is diff between defect management and defect tracking?
reply plz

Lakshmi

• Mar 26th, 2007

 

Defect management process is
Defect prevention, Deliverable Baseline, Defect Detection, Defect resolution, Process Improvement.

Where as Defect tracking is tracking the status of the defect until appropriate action is taken.