Project Estimation Technique

There are several estimation technique which differs based on project to project.

Some of the technique are:

1.    Expert Suggestion
2.    Historical Data
3.    Function Points
4.    Story Points
5.    Lines of Code
6.    COCOMO
7.    Use Case Points
8.    Wideband delphi
9.    Test case point 
10.  Parkinson Law 

Expert Suggestion
This is mos widely used technique.In this estimation technique, you have to rely on his expert experience.Based on his domain and technical capabilities he estimates things for multiple iterations until reached on some consensus.

Historical Data
Based on data available for similar project which has been delivered earlier.You have to compare if somewhat similar project has been completed earlier, approximately same amount of estimate will be for this project as well.

Function Points
In this Estimate technique we take multiple factors for deciding estimation.

Internal Queries
External Queries

based on no of input, output, enquiries, reading/writing  from internal database or reading from external read only database function points has already decided after several research we just have to count them & sometimes multiply by some adjust factor (based on implicit requirements like performance etc). After getting function points we multiply it by productivity factor ( how much function points in any particular will take how much efforts) & get required days or person months.Its one of most standard technique for estimation across industry).

Story Point 
This technique is mostly used in Agile methodology where we do relative estimate & give some points based on complexity.

There may be many scale & one common scale used as  Fibonacci series (1, 2, 3, 5, 8, 13, 21).  There could be other possible scale. More complex user story is more high number in series. Bigger then 13 or 21 can be break into smaller task.

Planning Poker is a estimation game in agile where we decide complexity with help of story point cards.

Software line of code. It may be physical means all the lines count including comment & blank line or may be logical which means executable line of codes.We may divide task to sub tasks to sub task & estimate line of code. It get counted in KLOC. 

Cocomo Model
This is very extensive estimation model which is available as basic, intermediate & advance sub models.

Use Case Points
In this technique we divide functionality based on use cases. We assigned some weight to use case category which could be simple, average, Complex, very Complex etc.  So after multiplying weigh factor to no of use cases of that category we get some estimations.

Wideband delphy
Team members give their individual advice. Based on their estimate we discuss why some one things its more complex & more time or someone who things its trivial & will take less time. Then we try to come at come consensus where everyone agrees about complexity & duration.

Test Case Point
In this technique we take test case as input.We estimate size of testing project project with this style or technique.

Parkinson Law
Count efforts on man months. This estimation is based on resource available. If a project required 10 month & we have 5 resource needed to work on it so work will be 50 man months.


Popular posts from this blog

Conversion from Clob To String in java and Vice versa

Portable Java 8/ JDK8 setup without admin rights

Multi Threading , Producer consumer problem in Java