Deliverables from the first team meeting and work assigned there. All due as soon as you can get them done - some today, all before the next class.

• Zero^th draft of a project web page, on which to post everything. (Put this in one of the team's public_html directories for now. It will move when the unix sysadmin creates the appropriate groups and directories.)

  Inform the class when it's ready, and when significant changes (new links, redesign) happen there.

  Note: all postings on this page are the collective responsibility of the team.

• Draft of letter (email) to the customer, to arrange a first meeting.

• Project name(s). Something memorable and pronounceable for the product you will build. Another one short and easy to type and remember for your unix group and project directory and CVS tree. These two names may (but need not) be the same. You'll have to clear the first one with the customer (eventually) but he need not know anything about the second one. The second should probably be all lower case (unix convention).

  If you can't find the right name right away make a list of possibilities and try them out with your friends and your customer.

• A bare bones schedule. (Posted on project web page.)

• A project to-do list, with individual assignments and completion dates. The items on this list should be the jobs that must be done to meet the first milestones on the schedule. (Posted on project web page.)

• Risk analysis. What are the major problems you foresee, and how might you go about preventing them? (Posted on project web page.)

• Preliminary thoughts on process: think about questions like: What kind of organization do you want? How will you divide responsibilities? How much XP do you want to do? How will you know that you are doing what you say you want to do? (Posted on project web page.)

• Minutes from the first meeting. (Posted on the project web page, of course.)

• Other items that occur to you ...perhaps as a result of our class discussion.

Back to the CS681 home page.