Ability to identify the hot spots of release from Bug Database

Bug Database for the products might have thousands of issues over a period of time against various builds and releases. Though these issues fixed over a period of time, it might be hard to derive meaningful metrics over the release.

We need to support these releases over the production systems & it might be helpful to capture the hotspots / risk elements with the release. Most of the issues here to deal with the respective features, compatibility with other features / technologies & performance related issues.

The usual metrics of number of issues against a module and their severity levels may not be of help always.

How easy is it to derive the following from the Bug Database for a given release

  1. Identify the issues have originated from Requirements, Design & Implementation
  2. Identify the issues over their category (Functional, Performance, Security, Compatibility, Usability etc)
  3. Identify the issues along with their origin & category over the features rather than the modules / components

Powered by ScribeFire.

1 Response to “Ability to identify the hot spots of release from Bug Database”


  1. 1 Vijay January 29, 2009 at 4:54 pm

    How do we define metrics for agile environment as it is very dynamic?


Leave a Reply





View Venkat Reddy Chintalapudi's profile on LinkedIn

Technorati

Add to Technorati Favorites

a

Blog Stats

  • 58,381 hits

Powerd By