Comments on: Estimation techniques compared http://www.st-webdevelopment.com/management/2010/01/estimation-techniques-compared/ Good software is only the beginning... Mon, 05 Jul 2010 14:33:17 +0530 http://wordpress.org/?v=abc hourly 1 By: basic cocomo http://www.st-webdevelopment.com/management/2010/01/estimation-techniques-compared/comment-page-1/#comment-5008 basic cocomo Fri, 02 Apr 2010 11:54:35 +0000 http://www.st-webdevelopment.com/?p=254#comment-5008 [...] services that will ... sections of the amendments and basic advice for creating a litigation ...Estimation techniques compared | Dominique StenderAn experience base comparison of three estimation techniques for IT projects. I compare PERT, COCOMO [...] [...] services that will … sections of the amendments and basic advice for creating a litigation …Estimation techniques compared | Dominique StenderAn experience base comparison of three estimation techniques for IT projects. I compare PERT, COCOMO [...]

]]> By: ManuelBS http://www.st-webdevelopment.com/management/2010/01/estimation-techniques-compared/comment-page-1/#comment-2637 ManuelBS Mon, 08 Feb 2010 10:32:30 +0000 http://www.st-webdevelopment.com/?p=254#comment-2637 Great article! I think for me, PERT is the best, because you can directly caclulate a price for small as well as for big projects. We have members in our team that allways have pessimistic estimation and some that always have optimisitic estimation, so PERT is really cool for us. But we will also try Planing Poker, but i think, only estimate the complexity may sometimes lead to wrong prices because you can have very easy taks (simply design 100 Pages) but that is not very complex but will take a lot of time. And it is the time and may be the risk of a task the customer has to pay. But that is only my point of view. Other opinions here? Great article! I think for me, PERT is the best, because you can directly caclulate a price for small as well as for big projects. We have members in our team that allways have pessimistic estimation and some that always have optimisitic estimation, so PERT is really cool for us.
But we will also try Planing Poker, but i think, only estimate the complexity may sometimes lead to wrong prices because you can have very easy taks (simply design 100 Pages) but that is not very complex but will take a lot of time. And it is the time and may be the risk of a task the customer has to pay.
But that is only my point of view. Other opinions here?

]]>