Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 01, 2013 12:37 PM by jammycakes
Jan 18, 2013 10:50 AM|LINK
Please suggest me, what are the common practices or methods to estimate effort (man hour) for an ASP.NET application? I am going to develop a mid size web application using Asp. NET. I have found some practices like Function Point etc. etc. but i want to
know what are the methods currently used in industry.
Jan 18, 2013 12:23 PM|LINK
Software Estimation in general might be one of the most difficult tasks in the entire world of development (if done properly and accurately).
The only person (or group of people) that can properly estimate how much effort, hours or time a project will take to complete depends completely on the group doing it.
There are a variety of factors such as the skill and experience of those on the project, their familarity with the tools and technologies being used, how well-planned and thought out the project and its requirements are, and how well the team members work
You can find an excellent discussion in the following Stack Overflow threads regarding Software Estimation for more information :
The Development Process - Estimating Software Costs in Man Hours
How to Get Better at Estimating Software (this discusses
using Evidence-based Tracking Software to help monitor your time)
Jan 22, 2013 03:00 AM|LINK
It is wise to split your major task in to sub taks. Estimations on sub task will be much easier and predictable than major task. Then percentage of deviation would be lower.
Feb 01, 2013 12:37 PM|LINK
Many people these days favour agile methods such as Scrum or Kanban.
You don't actually estimate the whole project up front, because that's like asking how long is a piece of string: you can only guess, and changing requirements (and make no mistake about it, they WILL change) and scope creep add a whole layer of uncertainty
into the mix.
Instead, you break the work down into chunks of, say, two weeks, called "sprints" and estimate these individually. There are techniques you can use to come up with estimates, such as Planning Poker, where each person on your team comes up with their own
individual estimate of how long it's going to take, and you come to a consensus based on that. Once you have done that, you then come to an agreement with the product owner as to what can be achieved and what should be expected in that time frame. Lather,