I had similar process when finding out my estimation factor. I also notices that my (positive) estimates are three times too short.
However, when I need to estimate time for group of people, even if I know them really well, and can estimate time for each of them individually, I would probably take a optimistic guess, multiply it by three and than take next time unit.
Yes, convert hours to days, days to weeks, weeks to months... Months would go to quoters or years, but you would already know that :-)
This technique proved very successful in estimating time for small team of 7 people with various skill levels. It also leaves enough time for testing, documentation and deployment :-)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.