This presentation enlightens the novel approach for estimation of QA time and resources. Numerous approaches e.g. Function Points Analysis, Feature points, Use Case points or Lines of Code (LOC) available in market specifically for project estimation but QA time and effort estimation generally done through past projects experience or simply through wild guess. Some time it gives correct estimation but the majority of time it confers lack of time for QA activities. This paper is an attempt to offer tiny step of concrete approach for QA estimation using priority of influence elements and impact factor.

1. Estimator Metrics
A Novel approach for QA estimation
Presenter’s
AMIT BHARDWAJ
Lead, Quality Engineering
TekMindz India Pvt. Ltd., Noida

2. Agenda
 Traditional QA Estimation [ Usually “Guess” Based]
 Probable Hurdles with traditional Approach
 “Estimator”, A novel approach for QA estimation
 Case Study : Implementation on “e-Insurance”, our on going
project.

3. Traditional QA Estimation
[ “Guess” Based ]
 Based upon past experience & expertise in technology.
 Based upon development cycle (60%-40%)
 Experience from repeated Production Customization activities
QA estimation based upon the above fact is fine! If and only if it is a
short term, less complex and low priority project.
A long term project with high priorities and complexities, shouldn't
be estimated based on the traditional guess based approaches.

4. Probable Hurdles with the Traditional
Approaches
 Estimation will be done more then once
(Inadequate estimation)
 Risk of Client back out
(Missing deadlines)
 Financial loss of organizations
 Multiple time estimation will affect Entire Project and
Business Plan

5. “Estimator Metrics”
A novel approach for QA estimation
It’s not rocket science!! Just precisely learn the art of using
ESTIMATOR !!
Following are the steps to achieve reliable effort estimation:
1. Constituent of Test Estimation
Constituent of Calculation of
2. Calculation Mechanism for Impact Test Estimation Impact Factor
Factor
3. Assumption for Degree of QA Assumption for Deg.
Of QA activities, Risk Identification of
activities, Risk Priorities & Priorities & Resultant QA activities
factor
Resultant Factor
4. Identification of QA activities
Preface of
5. Preface of Estimator Metrics Estimator Metrics

6. Step 1: Constituent of QA Estimation
The seven constituent of estimation has been identified, those having extreme tie with
estimation activities. It is recommended to review and keep in mind! Before moving
ahead!
 Approach
Test process, Test design techniques, Entry & Exit criteria and Test types
(RBT/SBT)
 Scope Approach
Functional, Performance, Migration and Localization
Client’s zeal
 Prerequisite Info for Quality
Scope
BRD /SRS/ Use Cases availability.
 H/W & S/W availability (Infrastructure Establishment) Constituent
Servers, licenses and equipments etc of QA
 Man Power Efficiency Risk &
Mitigation Estimation Prerequisite
Info
Domain expertise, Anticipated experience Plan
 Risk & Mitigation Plan
Infrastructure Investment, Documentation, Frequent Change Requests,
Man Power H/W & S/W
manpower backup Efficiency availability
 Client’s zeal for Quality
When to stop testing?? , Will agreed upon Adequate time & resources?

7. Step 2:
Calculation Mechanism
for Impact factor
High 8 I
Major
M
Medium 4 P
A
Low 2 C
Project
Priority
T
Onsite
Support
High 4
F
Complexity A
Impact Element
of work Minor
Medium 2
C
T
Technology
Low 1 O
R
QA Team
Classification of Degree of Risk Priority of Resultant Factor
Impact element Impact element Impact element

8. Step 2:
Calculation Mechanism for ..contd.
Classification of Impact element
A. Classification of Impact Element:
1. Project Priority :
Business impact. Security level OR simple e-Learning , Information search
applications
2. Complexity of Work : (Based on I/O Functions) Project
Banking/ Insurance /Mobile, and third party transaction Priority
involvement OR simple an employee
data mgmt , No third party transaction
Complexity Onsite
of work Support
3. Technology : Proven (Completely) OR New Classification
of Impact
element
4. Onsite Support (elective) : Available OR Not
5. QA Team :
Technology QA Team
Has enough professional experience and
domain as well as technical expertise OR
having intermediate expertise.

9. Step 2:
Calculation Mechanism for ..contd.
Degree of Impact Element
B. Degree of Impact Element
All right!! Now we have defined the impact elements, furthermore we need to identify
the valid degree for all the impact elements. (Prepare Standard Check List for the same)
 Major & Minor
Note : Major implies the soaring effort while Minor implies fewer effort .
1.Project Priority: Critical Business prospect of
application. Highly Secure application MAJOR QA Team
Simple e-Learning , Info Search App. MINOR Onsite
Technology
Support
2.Complexity of Work: Banking/ Insurance
Major
/Mobile, and third party transaction involvement Project
OR Complexity
Priority of Work
MAJOR Minor
Simple employee data management , No third
party transaction involved MINOR

10. Step 2:
Calculation Mechanism…contd.
Risk Priority of Impact Element
C. Risk Priority of Impact element
Now, we need to identify and categorize the risk involved for impact elements.
High
Risk Definition
High Risk: (Probability 70-100 %)
Would require high effort / time to handle the Major Medium
impact element.
Low
Medium Risk: (Probability 40-70 %) Degree of
Impact element
Would require average effort / High
time to handle the impact element.
Minor Medium
Low Risk: (Probability 0-40 %)
Discipline within the project is familiar with impact
element. Low

11. Step 2:
Calculation Mechanism ..contd.
Resultant Factor representation
D. Resultant Factor representation (A numeric representation for Risk Priority)
We opted to start the same with “1” (To avoid decimal calculation conflicts ).
It is entirely based upon iterative approach started from 1 to achieve the reliable test
estimation. (Fortunately, we got satisfactory outcome while started with “1” )
Low resultant factor for Minor degree as ‘1’, which is then subsequently increasing for
the respective combinations.

12. Step 2:
Calculation Mechanism …contd.
Metrics based on Degree of Impact element, Risk Priority & Resultant Factor
E. Metrics based on Degree of Impact element, Risk Priority & Resultant Factor
Below table demonstrates standard resultant factor’s for all the impact element
corresponding to measured (for hypothetical project) degree of impact elements

13. Step 2:
Calculation Mechanism for Impact factor
F. Calculation of Impact Factor
It’s simple, you need to add applicable resultant factor values and divide
the sum by total number of Impact element i.e. 5.
Impact factor = [ ∑ Impact Factors / No. impact element ]
Impact factor is calculated as (= 23 / 5) = 4.60
***Calculation for Deg. of Impact element, Risk Priorities and
Resultant Factor is based upon hypothetical project.

14. Step 3: Assumption for
Degree of QA activities,
Risk Priorities & Resultant Factor
To calculate Test time Estimation,
we need to define degree of QA
activities and corresponding risk
priority & resultant factors.

15. Step 4:
Identification of QA activities
"Quality" refers to all the good things that we would like to
see in our product. We build the product by assuring that its
quality was kept in mind by performing various activities at
different levels. Core QA activities can be defined as below:
• High Level Requirements / SRS / Use Case documents review
• Test Case Designing
• Test Case Execution / Updation
• Functional QA (Test Case execution, Regression)
More QA activities can be defined as per requirement. Available features
and functionalities can be broken down for respective QA activities.

16. Step 5: Preface of Estimator Metrics
Following are the
available feature /
functionality in the
application (assume):
 F1
 F2
 F3
Features will be broken
down for the respective
QA activates.

17. Case Study: Implementation of Estimator
on actual QA project

18. Case Study: Initial Guess Based
Estimation Submitted to Client
Initial Guess Based Estimation
Due to earlier Inadequate Estimation, we
forced to buy extra time from client to
complete the tasks.
First Estimation time = 87 days
forced to buy extra time = 30 days
Total time taken to finish the tasks = 117
QA time estimation for the QA activities using
Estimator = 122
Estimator approach seems
much better then earlier one
!!!

19. Thank You!
Presenter @ STC 2009:
AMIT BHARDWAJ
amitb.qa@gmail.com
Cell: +91-9818-622-019