Marcel provides some insights on estimating. It is sound advice, except that estimation is usually done at a time when nothing else in the project is decided, which actually is guesstimation. So when we do this estimation, we define many other dimensions, like the team’s composition, skill-set and process. [Continue]
Stu Smith gives excellent advice regarding deadlines and estimates. The only addition I would perhaps make is that treating estimation has a one-time activity hurts. More often than not software projects overrun their deadlines, and most of the times it is because of stale estimates. [Continue]
My answer for the weakest link in software development today is the estimation, and for various reasons. Most of the times the people who estimate and people who develop are different, their skillsets are different, and most importantly the business needs and constraints change at a higher frequency. Of course we know this, that is why agile development has flourished. [Continue]
Tom Hume talks about estimation in software development (via Rajesh Jain). Tom mentions creating worst, most likely and best case estimates to calculate the expected case. I was nodding while reading that statement. [Continue]