http://blogs.msdn.com/micahel/archive/2006/04/19/AnEspeciallyBadCaseOfEstimationGoneAwry.aspxLast year a convenience store near my house burned down. After a very long time (the insurance took forever to come through I guess) the wreckage was cleared away and a new building started going up. The exterior walls were done in a flash but the resten-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/micahel/archive/2006/04/19/AnEspeciallyBadCaseOfEstimationGoneAwry.aspx#579106Wed, 19 Apr 2006 19:34:26 GMT91d46819-8472-40ad-a661-2c78acb4018c:579106ShermanNoted... <br> <br>BTW, I tried our ur question on Ddj during my lunch hour while eating... it was fun! =)http://blogs.msdn.com/micahel/archive/2006/04/19/AnEspeciallyBadCaseOfEstimationGoneAwry.aspx#579112Wed, 19 Apr 2006 19:37:49 GMT91d46819-8472-40ad-a661-2c78acb4018c:579112ShermanHope I didn't embarrass myself too much in front of the expert =)http://blogs.msdn.com/micahel/archive/2006/04/19/AnEspeciallyBadCaseOfEstimationGoneAwry.aspx#579784Thu, 20 Apr 2006 13:47:29 GMT91d46819-8472-40ad-a661-2c78acb4018c:579784Jason Haleyhttp://blogs.msdn.com/micahel/archive/2006/04/19/AnEspeciallyBadCaseOfEstimationGoneAwry.aspx#581937Mon, 24 Apr 2006 09:42:03 GMT91d46819-8472-40ad-a661-2c78acb4018c:581937anuttharaAnother point worth noting is that often test costs are much more than the dev cost since the dev cost simply does not include the time taken for bug fixing. My manager often jokes that devs code for 6 weeks and then fix bugs for 6 months! <br>Testers will have to get their estimates right the first time around as well as convince their dev counterparts that it really does take so long to completely test the code they spew! :) I blogged on the same topic at <a rel="nofollow" target="_new" href="http://blogs.msdn.com/anutthara/archive/2006/03/28/562989.aspx">http://blogs.msdn.com/anutthara/archive/2006/03/28/562989.aspx</a>