Effort Estimation

You might also like

Download as xls, pdf, or txt
Download as xls, pdf, or txt
You are on page 1of 13

To Estimate effort we need to gather following testing aspects

1 Features to focus
Functional Requirement - 1
Functional Requirement - 2
Functional Requirement - 3
Functional Requirement - 4
Non-Functional Requirement - 1
Non-Functional Requirement - 2
2 Types of test to do
Functionality Test
Usability Test
Regression Test
Performance Test and so on
3 Development of Automated Scripts
Lets assume that we shall perform tests manually
4 Effort to design. Document test plan, scenarios / cases
We need to estimate effort for test plan, test design and test documentation.
5 Effort needed to document defects
Let us assume that we may find 80 defects in total.
Estimate effort for validating each requirement
Requirement
1 Functional Requirement - 1 (Description of the requirement)
2 Functional Requirement - 2 (Description of the requirement)
3 Functional Requirement - 3 (Description of the requirement)
4 Functional Requirement - 4 (Description of the requirement)
5 Non-Functional Requirement - 1: Should be highly usable
6 Non-Functional Requirement - 2: Performance
# Critical TS Effort/TS Pmins # High TS Effort/TS Pmins # Medium TS Effort/TS Pmins
30 15 20 15 15 10
25 20 20 15 10 10
15 10 10 10 5 10
8 10 5 10 5 5
5 10 5 10 5 5
10 10 5 5 5 5
# Trivial TS Effort/TS Pmins Effort PH
10 10 16.66666667
10 5 15.83333333
5 5 5.416666667
5 5 3
5 5 2.5
5 5 2.916666667
Estimate test documentation effort (person-hours)
1 Test plan documentation, review & correction (Planning) 8
2 Test scenarios documentation, review & correction (Design) 18
Assuming that it takes 3 hours for each feature
Documentation
Effort
26
Estimate Execution Effort (person-hours)
Let us assume that we have two incremental feature builds and two full builds
QA-C1 Functionality Test (FR1, FR2)
QA-C2 Functionilty Test (FR3, FR4)
Bug Fix Check
Usability
QA-C3 Bug Fix Check
Regression
Performance (If Applicable)
Documentation
QA-C4 Bug Fix Check
Regression
Buffer Time
UAT
Cycle
Bug Fix Check
Total Execution
Effort
0
5
10
15
20
25
30
35
1 2 3 4 5 6 7 8 9 10 11 12
Series1
32.5
32.5
8.416666667
13.91667
3
2.5
3
10.91667
2
2.916666667
3
3
13
2
8
4
4
74.33333
Series1
1
2
Estimate Defect Reporting and Management Effort (person-hours)
Defect Reporting
Let us guess that we may find 80 defects and each defect may take 10 minutes to record
Test Management
Let us assume that it takes 3 hours per cycle
Total Reporting and Management Effort
80*10 / 60 13
3 * 4 12
25
Strategy and
Planning
Design Automation Execution
8 18 0 74.33333333
Total Test Effort
8
18
0
74.33333333
25
0
10
20
30
40
50
60
70
80
1
H
o
u
r
s

Phases
Effort per phase
Reporting and Management
25
125.3333333
Effort per phase
Strategy and Planning
Design
Automation
Execution
Reporting and
Management

You might also like