QA on "the way" - What does 40% mean to projects??

[Global QA Team]

Provost, Shelley

Nov 23 2011

QA Effort Metric

The Validation effort should be no greater than 40%* of the Application Development effort on a project from Stage Gate 2 to Stage Gate 3.  This will be measured using hours logged to the PDM Development and Validation stages of a project. The purpose of the metric is to ensure QA efficiency and help bring focus to areas of QA involvement during a project that may need adjustment. *This metric may be adjusted based on product.

How the Rate is calculated:

Validation / Development + Validation

Where 

Development = all hours logged to the 08.x and 09.x Oracle task codes for a project
Validation    = all hours logged to the 10.x Oracle task codes for a project

[Global QA Team]

Provost, Shelley

Nov 23 2011 in response to Provost, Shelley

 Now my first question to this is how to get to 40% when you are testing on multiple platforms?

 

For example, it takes 10 hours to test enhancement A on Windows. If that enhancement is required to be tested on AIX and Solaris, that estimate and effort are now 30 hours.  I wonder if each platform should be a 1-off effort to make the 40%??  ideas? suggestions??

[Global QA Team]

Provost, Shelley

Jan 4 in response to Provost, Shelley

MOVING TO THE QA EFFORT METRIC DISCUSSION