Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are two types of estimates: <strong>task estimates</strong> and <strong>project estimates</strong>. You can view these as the big and small pictures.</p> <p>Project estimates are necessarily high level (granularity no smaller than days typically) and must include things like:</p> <ul> <li>High level architecture;</li> <li>Time for testing;</li> <li>Ramp up times;</li> <li>Defect processes;</li> <li>Time for documentation;</li> <li>Relevant training;</li> <li>Assumptions;</li> <li>Dependencies (eg team A can't do what they need to until team B delivers phase 1);</li> <li>Critical path (which pieces are likely to determine if the project slips and by how much); and</li> <li>Risks.</li> </ul> <p>The more of those things that are missing, the more unrealistic (or risky) the estimates.</p> <p>The second kind of a task estimate, which is typically much lower level. For this kind of estimate it should be simply a task breakdown (with no task being larger than say 5 days).</p> <p>These don't tend to address the above items but some of them might be relevant, such as assumptions regarding decisions not made yet (eg production hardware). It may also be worth identifying who can and can't do the tasks due to relevant experience, background knowledge or skills (as that person or those persons may end up overcommitted).</p> <p>Other posts have mentioned the testing time should equal or exceed dev time. I strongly disagree with this. I've seen 8 hour dev tasks result in 100+ hours test time and 80 hour dev tasks result in less than 2 hours of testing. In both cases the testing time was entirely reasonable. The is no absolute correlation between the two. At best, there is a loose connection.</p>
    singulars
    1. This table or related slice is empty.
    1. POEvaluating software estimates: sure signs of unrealistic figures?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScletus
    1. UScletus
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COEven smaller, I'd say. In a very large project this might be impractical, but task estimates in the range of a couple hours are very reliable in my experience.
      singulars
      1. PO
      1. USHanno Fietz
    2. COThe problem with detailed estimates is the cost of doing them, if you are not careful you spend as match estimating the 3 or 4 project you don't do, then programming the 1 that gets the goahead.
      singulars
      1. PO
      1. USIan Ringrose
    3. COThere's a tradeoff between speed and accuracy. Pick which matters to you.
      singulars
      1. PO
      1. UScletus
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload