I presented “Optimizing the Defect Lifecycle – with Resolution” to VANQ.org, the Vancouver Software Quality Assurance User Group. Subsequently I presented it to the Southern Idaho Society for Software Quality Assurance and UBC Continuing Studies (Tech.UBC.ca), and I wanted to share that material with you.
Just as defect reports provide valuable insight into the types of common classes of defects that have occurred in the past, analysis of other attributes can provide useful information for improvement. One of the classifications that can be applied to a defect would be its resolution.
Not all defects are simply fixed by development. Without specific tracking of defect resolutions, the true defect find rate and defect clustering in the code is obscured by duplicates, not repros, by designs, and enhancement requests.
In this presentation, we will look at the implications of how including a resolution attribute as part of your defect reports can help optimize the one of the core processes related to developing software. We will explore how we can use this field to facilitate process automation and data collection to help make team interactions more efficient and that the right people are making the decisions about product functionality.
You can download the slides on SlideShare.net: Optimizing the Defect Lifecycle – with Resolution
