![]() Typically, as part of traditional Project Planning, somebody will estimate the effort required for each task in the Work Breakdown Structure (WBS). Estimating Tasks on the Work Breakdown Structure Unfortunately there are many Project Managers out there estimating on behalf of their teams and I personally put more faith in the estimates from Technical Leads than the estimates from, often non-technical, Project Managers. According to Wikipedia: Software Development Effort Estimation there is only a 60-70% chance of the estimate being right even if the person is 90% sure of the estimate. It seems most people aren’t good at this. When using expert judgement the estimates are meant to be based on historical data of previous projects (if you have it) but normally the experts just rely on their memory. The more formal of the traditional approaches include COCOMO and Function Point Analysis (FPA), but in reality most estimates are based on expert judgement. Wikipedia: Software Development Effort Estimation has a pretty good summary of cost and effort estimation techniques. If you read one Agile book then read this one. “Agile Estimating and Planning” by Mike Cohn of Mountain Goat Software is the best book on Agile estimating there is. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |