Measuring Success How to use simple bug database queries and reports Some frequently used project-level measurements

Measure vs. Metric Measurements are compiled in an electronic spreadsheet, a database, or by hand Number of defects Metric: A calculated or composite indicator based on two or more measures, or a quantified measure of the degree to which a system, component, or process possesses a given attribute

Measure vs. Metric Metric: "a composite of measures that yields systematic insight into the state of processes or products and drives appropriate actions" average number of bugs per tester per day number of bugs found per area of the software ratio of Severity 1 bugs to Severity 4 bugs

Metric and Statistics Using the Information in the Bug Tracking Database Test manager or project manager want answers to these questions what types of bugs you're finding? what your bug find rate is? how many of your bugs have been fixed ? Which software tester has entered the most bugs? What areas of the software have the most bugs? Show a list of all the open Priority 1 bugs Does the software look like it's on track to meet the scheduled release date?

Metric and Statistics Performing queries is a powerful feature of a bug-tracking database Producing different charts is another way of getting information

Common Project-Level Metrics Management is fundamentally interested in the overall view of the project Software quality and reliability level Project on track to be ready as scheduled

Common Project-Level Metrics Chart that shows a breakout of the bugs found, separated into the major functional areas of the software

Common Project-Level Metrics

Common Project-Level Metrics