Time Estimates for Project Work

Before starting each project, please take a few minutes before each program to make an itemized estimate of how long you expect the work to take.   Then, keep track of how long it actually takes, and include both sets of figures in a text  file called estimates.txt with your project at turn-in.

You will not be graded on the accuracy of the estimate, but there will be a deduction if you don't.  I require a short list of whatever line items you care to track to justify your estimate.  Here is a sample of a pre-project estimate:

Hrs    Task
1      Make a windowless, featureless app with one visible button.
.5     Place app in sys tray
2      Randomly animate button with a timer (color, location, visibility)
1      Make an array of buttons like the first
2      Do delegate methods for buttons
1      Set button dimensions and counts based on screen resolution
1      Documentation
===
8.5
1.3    + 15%
===
9.8    Total Estimated Hours


This practice will help you develop a sense of how difficult certain things are and how much time you'll need if you, or others, are asked to do this kind of programming in a job situation.   The whole exercise shouldn't take more than 15 minutes of deep thinking.

RULES:

1. You must include your estimates as a separate text file, estimates.txt, zipped up with your project upon turn-in.  The estimate must contain two parts: pre-estimate, and actual time consumed.
2. Group projects must include an estimate of time from each team member.  A deduction will be made if a student's estimate is missing.  The distribution of effort will not be graded--only the presence of an estimate.
3. Estimates may be published to the class anonymously (that is, your name will not be on the estimate, but possibly it will be associated with the grade you were assigned for the work).

Visitors: