This reminds me of Buckminster Fuller's book 'The Critical Path'. The
first half is all about how you should careful record everything you
do, the second half talks about how to write down everything you do.
Making an estimate all boils down to knowing yourself. How do you
work? What is time consuming drudgery, what is exciting and engaging
for you? How GOOD are you at breaking up a project into component
I tend to go with flow charts sketched out by hand as my visual aid.
I do my best to estimate how long each of those boxes will take me to
complete. If it involves communicating with someone else or waiting
on input, I automatically double the estimate for that box.
Tally up the times and apply the Scotty factor (X 3). That is the
worst case scenario and that is the one I communicate to my
customers. The people knowledge here is spot on: Beat your estimate
and you are a hero, meet the estimate (through bad luck or unforeseen
disaster) and you are a valued member of the team who delivers on
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||