tag:blogger.com,1999:blog-7722108.post114786280058785638..comments2024-03-28T12:11:07.539+05:30Comments on Thinking Tester: A note on Test estimation ...Shrini Kulkarnihttp://www.blogger.com/profile/10782753752478547381noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-7722108.post-70370003784578117512008-04-30T11:03:00.000+05:302008-04-30T11:03:00.000+05:30In order to prevent the Creep in the Test Effort E...In order to prevent the Creep in the Test Effort Estimation the best way is to get the Test Plan reviewed by the Key Reviewers and stake holders. The initial estimation though should have the disclaimer as pointed out by the author.<BR/><BR/>Also keeping the disclaimer in the estimation sign off document truely provides the test manager to burgain for more resources or time if needed based on the Budget and Management will of the project.<BR/><BR/>Even if someone uses proven models like TPA for Test Estimation, someone needs to be judicious in terms of selecting the number of TCs and arrive at the effort estimation by keeping an eye on the cost/time factor.suvrahttps://www.blogger.com/profile/04700953504478968455noreply@blogger.comtag:blogger.com,1999:blog-7722108.post-25075902457718718572007-11-13T16:53:00.000+05:302007-11-13T16:53:00.000+05:30"Estimate means to form an approximate judgment or..."Estimate means to form an approximate judgment or opinion regarding the worth, amount, size, weight, etc., of calculate approximately."<BR/>The word itself is used to mean a rough figure, so I don't see any need to defend what has been put forth. Also it is well known fact that effort estimation is approximation, no matter what you adopt as method for achieveing it.The only way to get nearer to actual figure is to plough back what one learns from first estimate to next time one does the estimate for the same project (within the project lifecycle) ie you need to repeat the excercise a number time (at appropriate phase of the project).One will have better estimate of effort if he/she adopts the corrected estimate next time in a similar project (but then there are those who think no two project is similar!)<BR/>-shrinathAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7722108.post-1150498358414292362006-06-17T04:22:00.000+05:302006-06-17T04:22:00.000+05:30'Requirement Creep' and hence 'Testable Requiremen...'Requirement Creep' and hence 'Testable Requirement Creep' are the Project Liabilities, requiring change in the entire Project Plan and hence the Test Plan. Additional requirements are overheads to the project, which any Project Plan must include in words before sign-off by the customer. Any requirement that creeps in after the sign-off deserves the revision of the Project Plan. Horse-trading has to be done with the client concerned and the plan ought to be put forth to them.<BR/><BR/>The whole issue boils down to the crux of the problem - Effort Estimation, which depends on various factors;<BR/>* Experience of the test-team<BR/>* Complexity of the application<BR/>* Budget (Time/Cost)<BR/>* Management will et al<BR/><BR/>Estimation is something related to speculation (based on proven scientifc methods/heuristics). Speculation is a pure probability which is again a gamble.<BR/><BR/>As the saying goes - "Fail to plan; plan to fail", planning is required but nothing in this world is perfect. Certain amount of deviation goes in anything - by nature.<BR/><BR/>Realise this we are mere mortals. Athiests please excuse me :-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7722108.post-1150498302177247202006-06-17T04:21:00.000+05:302006-06-17T04:21:00.000+05:30'Requirement Creep' and hence 'Testable Requiremen...'Requirement Creep' and hence 'Testable Requirement Creep' are the Project Liabilities, requiring change in the entire Project Plan and hence the Test Plan. Additional requirements are overheads to the project, which any Project Plan must include in words before sign-off by the customer. Any requirement that creeps in after the sign-off deserves the revision of the Project Plan. Horse-trading has to be done with the client concerned and the plan ought to be put forth to them.<BR/><BR/>The whole issue boils down to the crux of the problem - Effort Estimation, which depends on various factors;<BR/>* Experience of the test-team<BR/>* Complexity of the application<BR/>* Budget (Time/Cost)<BR/>* Management will et al<BR/><BR/>Estimation is something related to speculation (based on proven scientifc methods/heuristics). Speculation is a pure probability which is again a gamble.<BR/><BR/>As the saying goes - "Fail to plan; plan to fail", planning is required but nothing in this world is perfect. Certain amount of deviation goes in anything - by nature.<BR/><BR/>Realise this we are mere mortals. Athiests please excuse me :-)Anonymousnoreply@blogger.com