ASP.NET Application - Time Estimation
We are creating an ASP.NET application.
Here I need to make a timing estimate for the whole application. I am currently using my past experience and some rules of thumb to get a rough estimate.
So now I doubt people are using past experience and a few rules of thumb to do this or using some common methodologies / practices like Cocomo or functional point analysis etc.
If you could please name the best links for them so I can go through them and start practicing.
Thank you very much! Respectfully. Bhavna.
source to share
The only way to get an accurate estimate is:
1) The work is (almost) identical to the task you did earlier.
2) Break down tasks until each task is less than 4 hours long.
(1) rarely, and (2) difficult!
Identify and manage your risks: Identify any unknowns or areas that are known (or likely to be) difficult. Monitor the progress of these tasks to minimize the impact on your project.
source to share
And don't forget that an appraisal is nothing more than an appraisal. It will never be 100% accurate. You can minimize and manage biases, as Mitch Peet said, but the bottom line is that an estimate should never be considered an exact thing. The problem is managing this principle convincingly :)
source to share
Function point analysis is good. But I usually take this approach.
Define roles in the system. Determine the Application Use Cases and the general and discrete use cases for each role. Bifurcate use cases in high medium low complexity. depending on your matrix of skills / mandalas that your organization has, you should be able to estimate the effort (number of mandalas). Depending on the effort and the number of people in the project, you can estimate the calendar days.
Don't forget about documentation, integration testing, system testing, peer reviews, user acceptance testing timings :)
source to share