The defect metrics derived from defect tracking tools like “Quality Centre” “Clear Quest” etc are important indicators of project quality. These metrics gives us the intended benefit only when they are analyzed, compared and interpreted in the right way. Many of these metrics like “Defect density”, “Defect severity index” etc need to be applied over the right set of data. Open defects entered in defect tracking system might get closed due to various reasons like environment issues, deployment issues, data issues, configuration issues etc. Still they are considered as defect but indicating different work groups involved in the project. When we need to improve the development and testing process, these metrics are to be applied over the coding issues and then analyzed. The closure code in the defect
tracking system is the key to start this analysis. This paper is about correlating the basic defect metrics and to trouble shoot different process parameters.

Suresh Srinivasan is an electrical engineer and holds a masters degree in business administration with over nineteen years of experience in Software Testing and Development. He has worked in different industry domains like manufacturing, Telecom, Insurance, Banking and Logistics. He started his career in testing and specialized in performance testing space. He is currently working as Chief Software Quality Analyst for Virtusa India Chennai. He has experience in establishing testing methodologies inheriting concepts from ATLM, TPI, TMAP and TMM. Metrics based process control is one of his favorite area. During his tenure he has also trained and developed several engineers on testing.