3 ms·
Breaking things down into smaller parts will help you estimate better. Also, sadly, just getting more experience will improve your estimating. Don't expect to
by chrisan 9y ago
Breaking things down into smaller parts will help you estimate better.
Also, sadly, just getting more experience will improve your estimating. Don't expect to be very accurate when you start. Most young developers, myself included, think "oh that will be no problem at all" and lowball everything.
There is a good question on StackOverflow to check out https://softwareengineering.stackexchange.com/questions/648/how-to-respond-when-you-are-asked-for-an-estimate https://softwareengineering.stackexchange.com/questions/648/...
- marcus_holmes 9y agoThe usual problem with this is that we tend to estimate based on difficulty, not effort. Building 10 web pages is "easy" because we know how web pages work, no problem. So we allocate half a day per page because it's just HTML, right? Designing a user interaction path through 10 different application functions isn't hard, but it takes a lot of communication and effort. Half a day per function is a tiny fraction of the effort required.