I use the following rules when I try to estimate developping time :
- No serious estimation without complete specs
- Don't assume that when you do several times the same thing you'll do it faster
(In fact you'll probably get bored and it will balance the speed gained by experience)
- No real task should be made professionnaly in less than half a day
(Real analysis,Test, Documentation...Not only implementation)
- Try to estimate the time to do each small task, sum up, then multiply by 2
(test, client interaction, integration...)
- If I don't have total control I can't produce correct estimation
(state it but try to give an estimation anyway :
"Provided the ISP had mod_perl properly configured it will take X hours, add X hours if I have to only use PHP...")
- Any addition to the specs will change the estimation
(even if they take something out, beccause your prior analysis and possibly data structure may be now inadequate...)
Following those guidelines have saved me several time.
" Only Bad Coders Code Badly In Perl" (OBC2BIP)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
