December 2002
Volume 5 • Number 1

Contents

PRACTITIONER NOTES
Defect Tracking and Management Process

by David Fern, Micros Systems, Inc.

INTRODUCTION

The purpose of a defect tracking and management process is to accurately and efficiently determine the state of the software and status of every known defect in the software at any given time. While this process is not the only tool for determining the software’s state, this article will focus on defect tracking and management during testing activities.

The defect tracking and management process records and tracks defects from their discovery through their repair and finally closure. Keeping track of thousands of defects is a difficult task and requires a process and tools to be managed correctly.

Tools such as the defect repository and periodic reports are mainly used to determine the state of the software, but they are also used as an archive on future projects. The team can better plan and react to situations by having metrics available from past projects. Metrics may include defect counts and percentages by module, defect turnaround times, and number of builds required to complete a project.

A defect tracking and management process can promote the resolution of issues in a systematic fashion, build teamwork, and create a record of the project that can be used in future projects.

The full text of this article may be found in the print journal. To subscribe go to /quality-press/display-item/index.html?item=SUBSCR_SQP .

Return to Top