Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Using three estimates can help. Create optimistic, likely, and pessimistic estimates for each significant development task. Plug the values into the Program Evaluation and Review Technique (pioneered from building Polaris nuclear submarines in the 1950s) to get a reasonable estimate:

t_{expected} = (t_{optimistic} + 4 \times t_{likely} + t_{pessimistic}) / 6

http://www.codecogs.com/latex/eqneditor.php

This also helps indicate what tasks will take the longest, allowing managers to prioritize based on business needs.



We used something a bit like this at IBM years ago. I'm pretty sure we weighted the pessimistic estimate higher than the likely estimate though.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: