From: Ethan Bolker <eb@cs.umb.edu>
To: cs681-1@cs.umb.edu
CC: paul@f7.net
Subject: to do lists
Date: Mon, 14 Oct 2002 21:25:11 -0400 (EDT)

In order to keep up the pace it's important to know what happens next,
even if you don't quite know what happens after that. 

>From now on I think each person on each team should always have a
to-do list, with several items on it, each with a completion date. As
things come off (because they're done) new ones should be added. The
list should always have some items with completion dates that are
soon, so that you never can say "there's nothing on my project that
needs to be done now".

The to-do lists can be maintained by the tracking system you use. I
think that will be sourceforge (more on that Wednesday) except for the
fotokey team, which is using quickbase.

So add to your agenda for your team meeting Wednesday the item that
says that everyone _leaves_ that meeting with a list of specific
tasks, with deadlines.

You should be writing lots of (short) use cases. They can be on
everyone's list if that suits.