Poll : average ASP.NET form dev time?
-
Does this sound familiar to anyone: You're faced with reviewing a spec for a large project and you're trying to come up with a ball park estimate. A common approach (usually combined with others) is to count the number of screens or forms that the project requires. Multiply that by some average number of hours you think it takes to do an ASP.NET form and you've got some starting point for your ball park estimate. Remember the goal is a superficial review and estimate with the understanding that there may be a large margin of error after a closer analysis of the spec. So what number do you use for the average number of hours to code an ASP.NET form (1.x or 2.0)? Assume both page and code-behind programming, but not design/CSS, etc. Just curious...
-
Does this sound familiar to anyone: You're faced with reviewing a spec for a large project and you're trying to come up with a ball park estimate. A common approach (usually combined with others) is to count the number of screens or forms that the project requires. Multiply that by some average number of hours you think it takes to do an ASP.NET form and you've got some starting point for your ball park estimate. Remember the goal is a superficial review and estimate with the understanding that there may be a large margin of error after a closer analysis of the spec. So what number do you use for the average number of hours to code an ASP.NET form (1.x or 2.0)? Assume both page and code-behind programming, but not design/CSS, etc. Just curious...
because i like to build whole apps in one page(lots of panels).
-
Does this sound familiar to anyone: You're faced with reviewing a spec for a large project and you're trying to come up with a ball park estimate. A common approach (usually combined with others) is to count the number of screens or forms that the project requires. Multiply that by some average number of hours you think it takes to do an ASP.NET form and you've got some starting point for your ball park estimate. Remember the goal is a superficial review and estimate with the understanding that there may be a large margin of error after a closer analysis of the spec. So what number do you use for the average number of hours to code an ASP.NET form (1.x or 2.0)? Assume both page and code-behind programming, but not design/CSS, etc. Just curious...
What I usually do when estimating is think of a project as similar as posibile with the one I need to estimate. And depending on the complexity add or remove hours to the estimation. If there's no comparison type, depending of the complexity of the pages: between 1 and 5 hours. Don't also forget to add some extra hours if your building a n-tier architecture. You need time for BLL, DAL also database design and implementation. What I usually do is add another 30% extra hours over the estimation. This gives you a good advantage in case you estimated incorectly some tasks. Well, this is me. If anyone has any recomendations, let me know. There's room for improvement for me too. regards, Mircea Many people spend their life going to sleep when they’re not sleepy and waking up while they still are.