Estimating Project Time
-
I am working on my business plan for a software project and would like advice on how to build a time schedule. We have already started working on a PERT chart and have an estimated time schedule, but we would like to compare it to some hard data. This project is extensive. It will be built from the ground up and is loaded with features. It will be marketed to the public. I realize it is hard to reply with an answer, otherwise I wouldn't be writing this thread in the first place. Comparisons of other people's past projects including corporate projects would be beneficial. Many thanks. Garrett
-
I am working on my business plan for a software project and would like advice on how to build a time schedule. We have already started working on a PERT chart and have an estimated time schedule, but we would like to compare it to some hard data. This project is extensive. It will be built from the ground up and is loaded with features. It will be marketed to the public. I realize it is hard to reply with an answer, otherwise I wouldn't be writing this thread in the first place. Comparisons of other people's past projects including corporate projects would be beneficial. Many thanks. Garrett
Estimating correctly is almost impossible without any prior metrics to base the estimates on. That said, I have used the following formula before, with some (limited) success:
Final Estimate = Original Estimate * 3Depending on the size of the team and your levels of experience, you can replace the 3 with any (larger) number you wish. :suss:
-
Estimating correctly is almost impossible without any prior metrics to base the estimates on. That said, I have used the following formula before, with some (limited) success:
Final Estimate = Original Estimate * 3Depending on the size of the team and your levels of experience, you can replace the 3 with any (larger) number you wish. :suss:
I have to agree with Steven. I find 3 to be a good multiplier for a fairly small team (3-5 people with above average experience) and a moderately large system (maybe 6 months to a year initially estimated). Those sizes and time lengths are simply my personal experience. I would say the longer the initial estimate or the more people involved, the larger the multiplier. Keep in mind, if you add more people, your initial estimate will probably get smaller, but your multiplier should probably go up by 1 for every 4 or 5 people you add). The reality is that in most cases, projecting a project's time, especially on a first project like this, is a shot in the dark. There are too many unknowns, not least of which is how well the team communicates and how much the individual members can contribute. Some people are more productive than others. You might end up with a very unproductive team, a very productive team, or something in the middle. Management may make a few alterations in the requirements, or they may make a lot. All these things can greatly affect the outcome. --"Beware of bugs in the above code; I have only proved it correct, but not tried it."- Donald Knuth
-
I am working on my business plan for a software project and would like advice on how to build a time schedule. We have already started working on a PERT chart and have an estimated time schedule, but we would like to compare it to some hard data. This project is extensive. It will be built from the ground up and is loaded with features. It will be marketed to the public. I realize it is hard to reply with an answer, otherwise I wouldn't be writing this thread in the first place. Comparisons of other people's past projects including corporate projects would be beneficial. Many thanks. Garrett