Browse Prior Art Database

Testing Estimation on Iterative Test Project Disclosure Number: IPCOM000189413D
Original Publication Date: 2009-Nov-09
Included in the Prior Art Database: 2009-Nov-09
Document File: 5 page(s) / 66K

Publishing Venue



This article introduces a method of how to do test estimation for iterative project. This method is developed based on the genearal idea of bottom-up estimation approach and focus on the testing effort estimation just in the iterations.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 41% of the total text.

Page 1 of 5

Testing Estimation on Iterative Test Project

The estimation method described here is for iterative testing projects with the following steps :

Step1: List all the tasks in iterative test project using WBS

Step2: Identify test efforts estimation factors (Expertise judgment and historical data )

Step3: Size the measurable units for the tasks in each iteration (Remeber to document assumptions ) Step4: Estimate efforts for each task ((Remeber to document assumptions )

Step5: Sum the estimated efforts of all tasks

Let's see the characteristics of the iterative projects before we go into details of this estimationmethod :

Each Iteration has a Requirement , Design, Coding, and Test phases

Each iteration is timeboxed , normally from 2 weeks to 8 weeks.

Since all the iterations are consecutive , the preparation of the next iteration and the execution ofthe current iteration have to be run in Parallel.

Since the iterative project is also accumulative , the regression test of the previous iteration has to be done during the current iteration in order to ensure the new functions deployed in the current iteration have not brought unexpected changes on the old functions deployed in the previous iteration .

Now let's turn to the details of this estimation method .



: Based on the characteristics of iterative testing projects , we can list all the tasks covered in them with WBS .


Page 2 of 5

Figure 1

* In-1 represents the previous iteration , In represents the current iteration , In+1 represents the next iteration .

Then in each iteration, the tasks may include: environment setup, the execution for the current iteration , the preparation for the next iteration and the regression for the previous iteration . Among them, the environment setup is not necessarily in the scope of the test team and the last 3 tasks should definitely be covered by test team in any project . The main focus of this invention is on the test efforts estimation of the last 3 task.



: Identify the testing estimation factors based on the expertise judgement and historical data .

These factors are identified for the iterative testing projects and the examples are given for the solution or application testing projects based on the practitioner 's expertise. For other kinds of testing projects , the values of the factors need to be adjusted to meet the project needs.

Based on the complexity of different components , we separate the components to be different categories (such as category1 and category2). Even for the same factor , the factor values may be different since the complexity and weight may be different for different categories . Based on the variance of different projects , we can set more categories if needed .


[This page contains 31 pictures or other non-text objects]

Page 3 of 5

Figure 2

Notes for factors explanation (i rep...