Standardized Defect Submission

Did you ever face any problem in defect review meeting; you were not able to explain the defect submitted by your own team members? You were in a situation to answer lot of questions from development and management which you are not sure or you don’t know?

I am sure you felt like you had answers for these questions like, “Is it happening for all the modules?”, “ Is it reproducible, if it is not reproducible what is the frequency of the specified defect ?”, “what is the impact” , “Is it on a particular hardware or environment ?”. Some times team members should have given all these details, but you don’t have the time to scan through the entire defect document and find in a shorter time you have in the defect review meeting.

The solution you can have to manage these kinds of circumstances, implement a standard format to submit the defect, so that you have most of the information handy, you can avoid the searching for the answers.

I am attaching a sample defect submission document which I made for our recent project, it was very helpful for us, and I had lots of fresher in my team, so it helped me to implement a standardized defect submission culture for the team, hope this will help you too. If the template is not much suitable for your scenarios, modify it or customize it to suite your needs.

Download the file from here : DefectSubmissionForamt.doc


This article can be found at the blog section of my personal site www.dileepk.info