View previous topic :: View next topic
|
Author |
Message |
raj_mainframe08
New User
Joined: 11 Sep 2007 Posts: 65 Location: Gurgaon
|
|
|
|
We need to prepare an estimate excel sheet that will give the hours needed estimate for a components. For example if a cobol components is entered and some properties of the change is entered i.e. small change, medium change etc, it gives the estimate of hours needed.
These kinds of sheet is used in many IT companies. If somebody can send me a sample sheet? |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
- what are you asking?
Quote: |
For example if a cobol components is entered |
where the component is entered? Did you mean - you write the name of some COBOL program in an excel and that should give you the estmation of "what"? |
|
Back to top |
|
|
raj_mainframe08
New User
Joined: 11 Sep 2007 Posts: 65 Location: Gurgaon
|
|
|
|
No, What i am asking is suppose i have to make an estimate of man hours needed to code a cobol program and the component in New and less complex. So i need to prepare a sheet where it will calculate the number of hours needed to code that cobol module. Similarly for other properties like medium complex, easy etc. Its just an initial estimation on the hours that may be needed and not the actual number of hours.
This sheet is different for different organizations. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Quote: |
This sheet is different for different organizations. |
Having said that, you should not ask for such a sheet on a public forum...IMHO.
Google on "Man Hours Estimate Worksheet" - you'll get some links to work with. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
suppose i have to make an estimate of man hours needed to code a cobol program |
As others have mentioned, this can vary greatly from one organization to another.
The time needed often depends on how things are accomplished within the organization. Some places have far more "overhead" than others.
One way to get an approximation is to base "this" estimate on the time it took to accomplish a previous similar requirement. This would assume that the person doing "this" work was of a similar calibre of the person who did the previous requirement.
Another thing to keep in mind is that people who are extremely fast at developing are very often extremely poor estimators. . . |
|
Back to top |
|
|
MBabu
Active User
Joined: 03 Aug 2008 Posts: 400 Location: Mumbai
|
|
|
|
in nearly 30 years, I've never been off by more than a week estimating a large project that I worked (alone) on (except once and that was a whopper of a misestimation but that was because I had control of the requirements and programmers always think of new requirements!), but I could not tell you how I did the estimates other than gut feel and the knowledge that I tend to work alone. How one would estimate work for others has always been a mystery to me and I've never done that well at all. I only say this to echo Dick's comments. The estimating process (and related information needed to gather on forms) is probably very different in every environment. Experience, processes, depth of documentation, testing, code reuse, data variability, number of systems, help resources, products or languages to integrate, etc, etc.
OK - that whole bit probably added nothing to the discussion - heck... I'm bored |
|
Back to top |
|
|
|