Test Estimation Techniques

Test Estimation TechniquesSl.No. Contents:

123456

Wide Band Delphi (WBD) Simple Medium Complex (SMC) Work Breakdown Structure (WBS) Three Point Estimation (3P) Hybrid Estimation_1 Hybrid Estimation_2

Project Name Wide Band Delphi/PERT Spreadsheet

Copyright 2005 IBM Corporation. All rights reserved. Version 1.0Page 2 of 30

Wide Band Delphi/PERT WorksheetEstimation Level: Low

Date: 15/04/2011

Estimators: 3WBS Risk Ranged Estimates Calculated Estimates

Estimator 1 Estimator 2 Estimator 3 Estimator 4

Project InitiationProject PlanningTest DesignTest Execution

Total 328.00 488.00 648.00 487.00 659.00 831.00 382.00 496.00 620.00 477.00 560.00 751.00 418.50 550.75

DetailsNo. of estimators 4Productive hours. per day 6.50

ExpensesTravel $0 Education $0 Hardware $0 Software $0

SummaryTotal effort hours 2963.00Total elapsed days 455.85

Note1. A red dot in the top right hand corner of a field represents additional notes. To view the notes, click the field you are interested in, then press Alt + I and then T.2. Green cells are calculated automatically. Do not enter data.

Project Name : RISProject Scope : Functional

Imp

ac

t (H

,M,L

)

Pro

ba

bil

ity

(H

,M,L

)

Op

tim

isti c

Mo

st

Lik

ely

Pe

ss

imis tic

Op

tim

isti c

Mo

st

Lik

ely

Pe

ss

imis tic

Op

tim

isti c

Mo

st

Lik

ely

Pe

ss

imis tic

Op

tim

isti c

Mo

st

Lik

ely

Pe

ss

imis tic

Op

tim

isti c

Mo

st

Lik

ely

Wide Band DelphiThe Wideband Delphi estimation method is a consensus-based technique for estimating effort.WBD Process:1.PlanningProject Manager selects a team of 3-7 team membersRepresentation from all groups like development, testing etcProject Manager should not be the moderator as he will have stake in the outcome of the estimation2.Kickoff meetingExplain the Delphi processReview the goals of the estimation sessionBrainstorm and note down the assumptionsGenerate the initial WBS3.Individual estimationEstimate the time required for each taskAdd any additional tasks to the WBSAdd any missing assumptions4.Estimation meetingModerator shares the estimates so that estimators can see the range of estimatesTeam members revises estimates based on group discussionsEstimates are revised until no estimator wants to changes his/her estimates.Estimators agree that the estimates are acceptable5.Assemble tasks and Review resultsProject Manager works with the team and collects the estimates from team membersCompiles the final WBS, estimations and assumptionsReviews the final estimates with the estimation team and reach consensus

Benefits:Build a complete task list or work breakdown structure for major activities.Consensus approach helps eliminate bias in estimates.Eliminate hidden agendas or divergent objectives for inexperienced estimators or influential individuals.Does not require historical data to prepare the estimates.Straightforward and Repeatable process

C4

Enter the name of the persons who participated in the estimating session.

B47

Enter how many people participated in the Wide Band Delphi session

B48

Enter the amount of productive hours per day







WBS


DetailsNo. of estimatorsProductive hours. per day

ExpensesTravelEducationHardwareSoftware

SummaryTotal effort hoursTotal elapsed days


Calculated Estimates Totals

620.00

313.00

1285.00

745.00

712.50 555.67 2963.00 2963.00

Pe

ss

imis tic

Ca

lcu

lat

ed

E

sti

ma

te sC

om

mit

te

d

Es

tim

ate s

Ph

as

e

To

tals



T7

The committed estimate is typed in manually. It represents the negotiated and agreed estimate for work elements.







WBS



ExpensesTravelEducationHardwareSoftware



Assumptions







Date Completed: Date Revised:

REQUIREMENT COMPLEXITY

VH Very High 2H High 1M Medium 0.5L Low 0.25

VL Very Low 0.25

EFFORT CALCULATIONREQ # REQUIREMENTS Complexity*****

6.1 Facilitates to raise request for break down maintenance M

6.2 Facilitates to raise, update, cancel and view a new biomedical break down request H

6.3 Facilitates to view the request history for a particular equipment with details L

6.4 Facilitates to view/list the requests raised location wise for a particular period M

6.5 Facilitates to view the status of the request raised. L

6.6 Facilitates to view the request and accept or reject the request. L

6.7 Facilitates to Allocate work to the Biomedical Engineer / Technician H

6.8 Facilitates to reallocate/ view the Work order allocated. H

6.9 Facilitates to view the work order assigned and launch closure screen L

6.9.1 Facilitates to document the task performed against the work order generated. H

7 VH

TOTAL EFFECTIVE TEST EXECUTION TIME (HRS)

Buffer estimated

TOTAL QC EFFORT (HRS)

DETAILS

No. of Resources 2Productive hours. per day 6.50

EXPENSES

Travel $0 Education $0 Hardware $0 Software $0

Project Name: Biomedical Equipment Maintenance (BME)Project Scope: FunctionalEstimation : Simple Medium Complex (SMC)

Time in Hours

Facilitates to launch/schedule preventive maintenance of equipment and enter details of new equipment, update the existing equipment details and condemn the equipment.

A7

Very High Complexity - Greater than 25 inputs/outputs per test case

C7

Time allocated for understanding one test case depending on the complexity of each requirement.

A8

High Complexity - Up to 25 inputs/outputs per test case

C8


A9

Medium Complexity - Up to 15 inputs/outputs per test case

C9


A10

Low Complexity - Up to 10 inputs/outputs per test case

C10


A11

Very Low Complexity - Up to 5 inputs/outputs per test case

C11


C16

Complexity, from a testability perspective, is based on the following: - How difficult is it to test the requirement? - Does it have any dependencies? - Is data required for testing this requirement? Is data available/accessible? - How will the requirement be tested? - How many test cases could be derived from the requirement? Entered by the Estimator.

B33

Patnaik: 10% - This takes care of delays in the build being delivered to QC and other issues

C40


SUMMARY

Total effort hours 153.92Total elapsed days 23.68

Date Completed: Date Revised:

ACRONYMS EXPLANATIONS

NTC Number of Test Cases (approximate)

UTC Review requirement/understand N test case(s)

DTC Design/write N test case(s)

RTC Run (execute) N test case(s)

%TCEF Probability of finding defects per N test case(s)

VTC Analyze, log and test defect(s)

ERE Re-execute test case(s)

ETC Total estimate for this requirement per N test cases

EFFORT CALCULATIONNTC UTC DTC RTC %TCEF VTC ERE ETC

6 3 2.25 1.5 0.00075 0.90 0.00 6.758 8 6 4 0.004 2.40 0.03 18.034 1 0.75 0.5 0.000125 0.30 0.00 2.256 3 2.25 1.5 0.00075 0.90 0.00 6.754 1 0.75 0.5 0.000125 0.30 0.00 2.254 1 0.75 0.5 0.000125 0.30 0.00 2.258 8 6 4 0.004 2.40 0.03 18.038 8 6 4 0.004 2.40 0.03 18.034 1 0.75 0.5 0.000125 0.30 0.00 2.258 8 6 4 0.004 2.40 0.03 18.03

10

20 15 10 0.02 6.00 0.32 45.32

70.00 62.00 46.50 31.00 0.43 139.93

13.99264

153.92

D16

NTC = Approximate number of test cases. This is dependent on the complexity of the requirement. The higher the complexity of requirements, the greater the number of test cases. Entered by the Estimator.

E16

UTC = Understanding Test Case This involves: Reviewing and understanding the Requirement + Determining software Requirement Testability + Understanding the Use Case + Understanding the Workflow Do not edit this field. This is calculated automatically as: Level of Complexity (time in minutes or hours) x NTC (# of test cases)

F16

DTC = Design Test Case This involves: Test Case Design and Writing with input and output/expected results Do not edit this field. This is calculated automatically as: 75% of UTC

G16

RTC = Run (execute) Test Case This involves: Executing functional/integration test case(s) + Familiarity with application + Revising test case(s) Do not edit this field This is calculated automatically as: 50% of UTC

H16

%TCEF = Probability of finding defects per N test cases What is the % probability of finding defects per N test cases How many defects are likely to be detected per N test cases Do not edit this field This is calculated automatically as: Level of Req Complexity (in minutes or hours) / 1000 x RTC

I16

VTC = Verify Test Case Defects This involves: Verifying suspected defect(s) before entering in the defect tracking system + Defect retest Do not edit this field This is calculated automatically as: 60% of RTC

J16

ERE = Re-Execute Test Cases Do not edit this field This is calculated automatically as: %TCEF x (RTC + VTC)

K16

ETC = Total estimate for this requirement per N test cases. Do not edit this field. This is calculated automatically as: UTC + DTC + RTC + ERE

D30

Total number of test cases.

E30

Total effort for all requirements and test cases.

F30


G30


J30


K30




Work Breakdown Structure (WBS)

WBS Tasks

Project InitiationScope of Testing

Requirement Study Test Lead, Test Engineer 20.00 30.00 40.00 30.00

IN & OUT of Scope Test Lead, Test Manager 8.00 12.00 16.00 12.00

Identify Risks Test Lead, Test Manager 8.00 12.00 16.00 12.00

High Level Estimation Test Manager 6.00 8.00 10.00 8.00

Requirements Analysis

Requirement session Test Lead, Test Engineer, Test Manager 4.00 6.00 8.00 6.00

Requirement Review Test Lead, Test Engineer, Test Manager 20.00 30.00 40.00 30.00

Create MBT Test Engineer 12.00 16.00 20.00 16.00

Requirement Decomposition Test Engineer 12.00 16.00 20.00 16.00

Project PlanTest Planning

Scope of Testing Test Lead, Test Manager 4.00 8.00 12.00 8.00

Master Test Plan Test Lead, Test Manager 8.00 12.00 16.00 12.00

Test Scenarios Test Engineer 12.00 16.00 20.00 16.00

Review & Rework Test Plan Test Lead, Test Manager 8.00 12.00 16.00 12.00

Test Estimation

Estimate testing project size, effort, cost & schedule Test Lead, Test Manager 6.00 8.00 10.00 8.00

Compare estimations Test Lead, Test Manager 3.00 4.00 5.00 4.00

Review & Rework Estimation Test Lead, Test Manager 4.00 6.00 8.00 6.00

Test DesignReview & rework Test scenarios Test Engineer 8.00 12.00 16.00 12.00

Test design technique Test Engineer 3.00 4.00 5.00 4.00

Prepate test cases Test Engineer 40.00 60.00 80.00 60.00

Review & Rework test cases Test Engineer 20.00 40.00 60.00 40.00

Test EnvironmentHardware & Software setup Test Lead, Test Engineer 4.00 6.00 7.00 5.83

Build Install mechanism Test Engineer/BR Team 1.00 2.00 2.50 1.92

Test data setup Test Engineer 1.00 2.00 2.00 1.83

Test ExecutionSIT Cycle

Functional Round 1

Start BVT Test Engineer/BR Team 1.00 1.50 2.00 1.50

Test Execution Test Engineer 40.00 60.00 80.00 60.00

Log defects Test Engineer 2.00 3.00 4.00 3.00

Project Name : RIS Estimation Level: LowProject Scope : Functional Date: 15/4/2011Estimators: 3

Team(s), Role(s) or Individual(s) Responsible for Execution of Task

Best Case Estimate (hrs)

Most Likely Estimate (hrs)

Worst Case Estimate

(hrs)

Expected Case Estimate

(hrs)

B4


G5

Best case+worst case+(4*Most likely))/6



Generate Test Report Test Engineer 1.00 2.00 2.00 1.83

Functional Round 2


Defect Verification Test Engineer 3.00 4.00 5.00 4.00

Defect Correction Test Test Engineer 30.00 40.00 50.00 40.00



Functional Round 3


System functional testing Test Lead, Test Engineer 40.00 60.00 80.00 60.00

Compatibility Testing Test Engineer 6.00 7.00 8.00 7.00

Security Testing Test Engineer 8.00 10.00 12.00 10.00

End to End Testing Test Engineer 8.00 10.00 12.00 10.00



Post Deployment Testing

Production Test environment setup Test Lead, Test Engineer 4.00 6.00 7.00 5.83


Start BVT Test Engineer 1.00 1.50 2.00 1.50




Other activities

Defect Review Meeting Test Lead, Test Manager 12.00 14.00 16.00 14.00

Project Status Meeting Test Lead, Test Manager 12.00 14.00 16.00 14.00

Daily Stand up meeting Test Lead, Test Manager, Test Engineer 10.00 12.00 12.00 11.67

ReleaseRelease Notes Test Lead, Test Manager 2.00 3.00 3.00 2.83

Test Summary Test Lead 1.00 2.00 2.00 1.83

RTM Generation Test Lead 3.00 4.00 4.00 3.83

Project ClosureLessons learnt Test Lead 2.00 3.00 4.00 3.00

RCA study Test Lead 3.00 4.00 5.00 4.00

419.00 610.00 786.50 607.58

DetailsNo. of estimators 3Productive hours. per day 6.50

ExpensesTravel $1 Education $1

Work Breakdown StructureA work breakdown structure (WBS), in project management and systems engineering, is a deliverable oriented decomposition of a project into smaller components. It defines and groups a project's discrete work elements in a way that helps organize and define the total work scope of the project.

The Work Break down structure should include any and all tasks that are within the scope of the Project, which is being estimated.1).Break sizing into smaller, easier to estimate tasksa.Decompose the test project into phases.b.Decompose each phase into constituent activitiesc.Decompose each activity into tasks and subtasks until each task or subtask at the lowest level of composition2).Taking risk priority into accounta.Set up dependenciesb.Dependent tasks internal to the test subproject.c.Document dependencies, resources, and tasks external to the test subproject (i.e., those that involve collaborative processes )3) Estimate the effort in person-hours. The Result of various tasks involved in step 1 is an effort estimate in person hours. The effort of various Project tasks expressed in person-hours is also influenced by various factors such as:a) Experience/Capability of the Team members b) Technical resources c) Familiarity with the Tools, Techniques and Technology platform4) Estimate the schedule in calendar months The Project Planners work closely with the Technical Leads, Project Manager and other stakeholders and create a Project schedule. Tight Schedules may impact the Cost needed to develop the application.

This is Bottom - Up Strategy for Test Estimation. The technique is called bottom-up since based on the tasks which is at the lowest level of the work breakdown hierarchy you estimate the duration, dependencies and resources. In bottom up strategy, estimates are not taken by a single person but all stakeholders , individual contributors , experts and experienced staff members collectively. The idea is to draw on the collaborative wisdom of the team members to arrive at accurate test estimates

B79

Enter how many people participated in the WBS

B80




Hardware $1 Software $1

SummaryTotal effort hours 607.58Total elapsed days 93.47







WBS




Test Estimation

Test Design

Test Environment


Functional Round 1

Assumptions



Functional Round 2

Functional Round 3


Other activities

Release

Project Closure


ExpensesTravelEducation






HardwareSoftware








Three Point Estimation

Tasks

Earned Value

Project InitiationScope of Testing Requirement Study Test Lead, Test Engineer 20.00 30.00 40.00 30.0

IN & OUT of Scope Test Lead, Test Manager 8.00 12.00 16.00 12.0

Identify Risks Test Lead, Test Manager 8.00 12.00 16.00 12.0

High Level Estimation Test Manager 6.00 8.00 10.00 8.0

Requirements Analysis 0.0

Requirement session Test Lead, Test Engineer, Test Manager 4.00 6.00 8.00 6.0

Requirement Review Test Lead, Test Engineer, Test Manager 20.00 30.00 40.00 30.0

Create MBT Test Engineer 12.00 16.00 20.00 16.0

Requirement Decomposition Test Engineer 12.00 16.00 20.00 16.0

Project Plan 0.0

Test Planning 4.00 8.00 12.00 8.0

Scope of Testing Test Lead, Test Manager 8.00 12.00 16.00 12.0

Master Test Plan Test Lead, Test Manager 12.00 16.00 20.00 16.0

Test Scenarios Test Engineer 8.00 12.00 16.00 12.0

Review & Rework Test Plan Test Lead, Test Manager 0.0

Test Estimation 0.0

Estimate testing project size, effort, cost & schedule Test Lead, Test Manager 6.00 8.00 10.00 8.0

Compare estimations Test Lead, Test Manager 3.00 4.00 5.00 4.0

Review & Rework Estimation Test Lead, Test Manager 4.00 6.00 8.00 6.0

Test Design 0.0

Review & rework Test scenarios Test Engineer 8.00 12.00 16.00 12.0

Test design technique Test Engineer 3.00 4.00 5.00 4.0

Prepate test cases Test Engineer 40.00 60.00 80.00 60.0

Review & Rework test cases Test Engineer 20.00 40.00 60.00 40.0

Test Environment 0.0

Hardware & Software setup Test Lead, Test Engineer 4.00 6.00 7.00 5.9

Build Install mechanism Test Engineer/BR Team 1.00 2.00 2.50 2.0


Test Execution 0.0

SIT Cycle 0.0

Functional Round 1 0.0





Project Name : RIS Estimation Level: LowProject Scope : Functional Date: 15/4/2011Estimators: 3

Methodology Stage or Activity Team(s), Role(s) or Individual(s)

Responsible for Execution of TaskBest Case

Estimate (a) Most Likely

Estimate (m)Worst Case Estimate (b)

B4


D5

Effort in hrs

E5

Effort in hrs

F5

Effort in hrs





Defect Verification Test Engineer 3.00 4.00 5.00 4.0

Defect Correction Test Test Engineer 30.00 40.00 50.00 40.0





System functional testing Test Lead, Test Engineer 40.00 60.00 80.00 60.0

Compatibility Testing Test Engineer 3.00 4.00 4.00 3.9

Security Testing Test Engineer 4.00 5.00 6.00 5.0

End to End Testing Test Engineer 8.00 8.00 10.00 8.4



Post Deployment Testing 0.0

Production Test environment setup Test Lead, Test Engineer 4.00 6.00 7.00 5.9


Start BVT Test Engineer 1.00 1.50 2.00 1.5




Other activities 0.0

Defect Review Meeting Test Lead, Test Manager 12.00 14.00 16.00 14.0

Project Status Meeting Test Lead, Test Manager 12.00 14.00 16.00 14.0

Daily Stand up meeting Test Lead, Test Manager, Test Engineer 10.00 12.00 12.00 11.7

Release 0.0

Release Notes Test Lead, Test Manager 2.00 3.00 3.00 2.9

Test Summary Test Lead 1.00 2.00 2.00 1.9

RTM Generation Test Lead 3.00 4.00 4.00 3.9

Project Closure 0.0

Lessons learnt Test Lead 2.00 3.00 4.00 3.0

RCA study Test Lead 3.00 4.00 5.00 4.0

Totals 599

E (Project Work) 599.00SD (Project Work) 16Project Estimate > 95% Confidence 725

Three Point EstimationThree Point Estimation technique is based on statistical methods, and in particular, the Normal distribution. In Three Point Estimation we produce three figures for every estimate:a = the best case estimatem = the most likely estimate b = the worst case estimate These values are used to calculate an E value for the estimate and a Standard Deviation (SD) where:E = (a + (4*m) + b) / 6SD = (b - a)/6E is a weighted average which takes into account both the most most optimistic and pessimistic estimates provided and SD measures the variability or uncertainty in the estimate. To produce a project estimate the Project Manager:Decomposes the project into a list of estimable tasks, i.e. a Work Breakdown Structure Estimates each the E value and SD for each task. Calculates the E value for the total project work as E (Project Work) = Σ E (Task) Calculates the SD value for the total project work as SD (Project Work) = √Σ SD (Task) 2 We then use the E and SD values to convert the project estimates to Confidence Levels as follows:Confidence Level in E value is approximately 50% Confidence Level in E value + SD is approximately 70% Confidence Level in E value + 2 * SD is approximately 95% Confidence Level in E value + 3 * SD is approximately 99.5%

Enter the a,m, and b values for each Task into columns C,D and E. The E and SD values for each task will be calculated and displayed in columns F and G. A task estimate with at least 95% confidence and the required task booking value is calculated and displayed in columns H and J.

Based on the individual task estimates the E value and SD for the project will be calculated and displayed as will the overall work estimate for the project with at least 95% confidence levels.











Test Estimation

Test Design

Test Environment


Functional Round 1

Methodology Stage or Activity

SD Value SD**2

3.4 36.8 11.60

1.4 14.8 2.00

1.4 14.8 2.00

0.7 9.4 0.50

0.0 0.0 0.00

0.7 7.4 0.50

3.4 36.8 11.60

1.4 18.8 2.00

1.4 18.8 2.00

0.0 0.0 0.00

1.4 10.8 2.00

1.4 14.8 2.00

1.4 18.8 2.00

1.4 14.8 2.00

0.0 0.0 0.00

0.0 0.0 0.00

0.7 9.4 0.50

0.4 4.8 0.20

0.7 7.4 0.50

0.0 0.0 0.00

1.4 14.8 2.00

0.4 4.8 0.20

6.7 73.4 44.90

6.7 53.4 44.90

0.0 0.0 0.00

0.5 6.9 0.30

0.3 2.6 0.10

0.2 2.3 0.10

0.0 0.0 0.00

0.0 0.0 0.00

0.0 0.0 0.00

0.2 1.9 0.10

6.7 73.4 44.90

0.4 3.8 0.20

0.2 2.3 0.10

Task Estimate 95%

Confidence



Functional Round 2

Functional Round 3


Other activities

Release

Project Closure




0.0 0.0 0.00

0.2 1.9 0.10

0.4 4.8 0.20

3.4 46.8 11.60

0.4 3.8 0.20

0.2 2.3 0.10

0.0 0.0 0.00

0.2 1.9 0.10

6.7 73.4 44.90

0.2 4.3 0.10

0.4 5.8 0.20

0.4 9.2 0.20

0.4 4.8 0.20

0.2 2.3 0.10

0.0 0.0 0.00

0.5 6.9 0.30

0.2 2.3 0.10

0.2 1.9 0.10

0.2 6.3 0.10

0.4 3.8 0.20

0.2 2.3 0.10

0.0 0.0 0.00

0.7 15.4 0.50

0.7 15.4 0.50

0.4 12.5 0.20

0.0 0.0 0.00

0.2 3.3 0.10

0.2 2.3 0.10

0.2 4.3 0.10

0.0 0.0 0.00

0.4 3.8 0.20

0.4 4.8 0.20

725

Hybrid Test Estimation (Delphi & Size based)

Test Basis Best Case Optimized case Worst case Expected case# Requirements 120 120 120 120Speed TCD 3 2 1 2Speed TCE 8 5 3 5.166666666667Resources taken into account 2 2 2 2

Average TC's per Reqmt 8 8 8 8

Size (#Testcases) 960 960 960 960

Tasks Best Case Optimized case Worst case Expected caseRequirement Analysis 60 60 60 60Test Case Design 320 480 960 533.3333333333Test Execution (FR1) 120 192 320 201.3333333333Defect Correction Testing (FR2) 40 64 106.6666666667 67.11111111111System Testing (FR3) 120 192 320 201.3333333333

TOTAL EFFORT (Hours) 660 988 1766.67 1063.111111111TOTAL EFFORT (Days) 101.5384615385 152 271.7948717949 163.5555555556TOTAL EFFORT (Person Days) 50.76923076923 76 135.90 81.77777777778

Dependencieson the quality of unit testingproper code reviewsProper design and reviewson component integration testingon timelines for deliverable by PDon quality of skill of resourceson tracebility and dependency matrix for all features by PM and PD

Risks involved Unstablility of Test environment unplanned builds to QC

Scope creep based on baselined requirements Unplanned CR's Resource non-availability

Delphi & Size based estimation

This Estimation technique is a mixture of Delphi and Size based, taking into account prev history and experience and then arriving at three figures (Best, Optimized and worst)for every estimate.

Scope/Basis:No of Reqmts/Usecases/CR's/Defects

Size determination:Derive #TC's to be designed using level of reqmts/#Usecases/#CR's/#Defects Defect Prediction:30% failure rate (New project)Predictive Rayleigh Model Effort determination (Test case design & Test execution):Speed (tc/hr) - Ask the team on the speed for Best, Worst and Optimal casesSize(#tc’s) Schedule:Effort(hrs) = Size/Speed# Resources Timelines:Start DateEstimated days for CompletionCompletion Date

E3

(Best case+worst case+(4*Optimized case))/6





Testing Phase TasksRequirement Analysis & Review

TC/hr DecompositionTC/hr Test Design Test Scenario

Test cases

Review

Test Environment InstallationTest Data setup

Remarks Test Execution FunctionalEffort in Hrs IntegrationEffort in Hrs SystemEffort in Hrs Defect LoggingEffort in Hrs Defect ReviewEffort in Hrs Reports Test Reporting

RTM

Requirement Levels consideredLevel 1 - 16TC's Level 1 - 9TC'sLevel 2 - 12TC's Level 2 - 6TC'sLevel 3 - 8TC's Level 3 - 3TC'sLevel 4 - 4TC's









Hybrid Test Estimation (Delphi & Size based)

Project RIS #TC's/Reqmt

Scope of Project SIT Estimation Approach

Modules targeted 1 Estimation Phase

No. of Requirements 120 Estimation Risk

Project Start Date 25-Sep-10 No.of Resources

Effort DistributionCoverage Maximum Optimized BasicInitial WP Size 960 960 960Effort Person Hour 320 480 960Effort Person Day 49 74 148

Tasks Person Days Person Days

Documentation 15.00% 48.00 7.38 72.00 11.08 144.00Req. Understanding 20.00% 64.00 9.85 96.00 14.77 192.00Design 25.00% 80.00 12.31 120.00 18.46 240.00Review 5.00% 16.00 2.46 24.00 3.69 48.00Execution 20.00% 64.00 9.85 96.00 14.77 192.00Non-Project 15.00% 48.00 7.38 72.00 11.08 144.00Total 100% 320.00 49.23 480.00 73.85 960.00No.of Days 25 37Estimated Finish Date 26-Oct-10 11-Nov-10

Effort Distribution

Effort Person Hours

Effort Person Hours

Effort Person Hours





B12

Size=#Reqmts x TC's for Reqmt level

D22

Effort=(Size/Speed)





8 LegendHybrid Speed 3 Size

Initial Speed 2 Speed

Medium Speed 1 Effort

2

Assumptions:Effort DistributionBasic Note Enter data only in yellow cells960960148

Person Days

22.1529.5436.927.38

29.54

22.15147.69

7428-Dec-10

Requirements are level 3. 6.5hrs productive hours per person day.









Legend# Reqmts * #TC's/reqmt#TC's/hrSize/Speed

Enter data only in yellow cells

Requirements are level 3. 6.5hrs productive hours per person day.

Documents

Test Estimation Techniques