Page 52 -

factor in creating the schedule is taking into account necessary delays in which no work
will be done. For example, the team may need to wait for a server to be built or a software
licensing agreement to be reached; estimates for any known waiting time can also be added
to the preparation results.
Any effort related to project overhead should not be taken into account. This includes
things like status meetings, reports, vacation, etc. A separate estimation session can be
held for overhead. Any time an estimator identifies a project overhead task, it should be
added to the “Project overhead tasks” section of the preparation results. Similarly, estima-
tors may run across potential delays, because certain tasks can’t start until after specific
dates. These should be added to the “Calendar waiting time” section, and not taken into
account while making estimates. (Often, a separate Delphi session will be held specifically
to estimate waiting time or overhead tasks. This is the purpose of the checkboxes at the
top of the estimation form in Figure 3-2.)

Name Date Estimation form
Goal statement Units
Category goal tasks quality tasks waiting time project overhead
WBS# or Delta Delta Delta Delta
priority Task name Est. 1 2 3 4 Total Assumptions

Delta
Total

FIGURE 3-2. Filled-in estimation form
( The Process Group, copied with permission)
©
While estimating each task, most people realize that they must make additional assumptions
in order to estimate tasks. These should be recorded in the “Assumptions” section of the
preparation results. They may also discover additional tasks that were not found during the
kickoff meeting—these missing tasks should be added to the “Task list” section and esti-

44 CHAPTER THREE