Schedule

       A schedule answers many of the questions, that goes into organizing a larger job: who does what when and for how long - the last one is tough, and can only be learned from practice. The schedule also organizes the deadline.
       Curt, 14 hours, database design, after October 15, finished by November 1.
       Curt, 5 hours, write test plan, after October 25, finished by November 5.
       Peter, 5 hours, write test plan, after October 25, finished by November 5.
       Etc.
       A good supplement for a schedule is the action of registering time, where you note as accurately as possible the time for an activity, and who did it when. This makes it possible to go back and check up on the quality of the time estimates (guesses), as the schedule was made - and that makes the estimates better next time.
       A time register should be as accurate as the schedule. It's fair to count hours.
       Wednesday, Curt, 3 hours, database design.
       Thursday, Curt, 4 hours, database design.
       Thursday, Curt, 2 hours, write test plan.
       Thursday, Peter, 1 hour, write test plan.
       Etc.

Concept last updated: 08/08 2003.

Relations
is a kind of
is one of the tools in

Other sources

Router Schedule Select

Libellus