Testing Effort Estimation
This estimation process outlines the general methodology by which Manager/Lead develops realistic estimates of the effort, for respective stage of a project. Estimation is done to determine the following, which may be needed to complete a project/task.
- Resources (e.g. computers, software licenses, etc.)
- Schedule / Timeline
Two methods for estimation have been described in the following process – Work Breakdown Method and Function Point/Testing Point Analysis.
Work Breakdown Method
It is created by breaking down the test project into small pieces. Modules are divided into sub-modules. Sub modules are further divided into functionality and functionalities are divided in sub-functionalities.
Review all the requirements from Requirement Document to make sure they are added in Work Breakdown Structure. Now you figure out the number of tasks your team needs to complete. Estimate the duration of each task.
Function Point/Testing Point Analysis
The FP technique is a direct indicator of the functionality of software application from the user’s perspective. This is the most accepted technique used to estimate the size of a software project.
Base of this technique is function point technique. Here we convert function points into test points. In Test Point analysis, we usually carry out the following:
- Dynamic Test Points
- Static Test Points
- Environmental Factor
- Productivity Factor
- Primary Test Hours
- Control Factor
- Total Test Hours
For any software testing estimation technique, it is highly recommended that following factors should be taken into account:
- Domain Knowledge and core requirements
- Risks and complexity of the application
- Team Knowledge on the subject/skills
- Historical data for the previous estimation for improvement and accuracy
- Estimation should include buffer time
- Bug cycles for the project
- Resources availability