- Determined we need user stories soon so that we can begin writing
scopes, plans, flow diagrams, etc.

- Ed (Coach) must determine if we can have greater than 1 customer.

- Since Al is the tracker, and taking measurements, he will also
  take on the role of boss.

- Ian (Customer) should contact the customer and begin work on user
  stories.

- Because of the importance of the customer & user stories right now,
  Drew would also like to be a customer.  For now, he will try to
  contact the customer and begin work on user stories.  Ian, would you
  like to move from customer to developer?  We think that you're the
  busiest one on the team w/ your two semester projects.  But we need
  user storiest soon.  Ed (Coach) says that XP allows more than one
  customer on a team, but we must determine if two customers is optimal.

- Al will e-mail the TA with the following questions.

  - What documents should we produce for our project?  Because XP has
    no established artifacts, we are a little confused on what to produce
    (besides the obvious like user stories & unit tests). Should we just
    produce whatever we feel is necessary? (Software Scope, various
    diagrams, etc.?)

  - Since XP has no artifacts, what checkpoints are we supposed to
    establish?  Are these checkpoints that we establish ourselves or
    with you the TA?

  - Are we allowed to change roles of individuals within our group?
    One team member is a little busier than the rest and we feel it
    would be best if someone else takes over the role of customer
    (since we need the customer to do user stories quickly).

- Plan is to have some user stories ready by next weekend, so that we can
meet as a group on Sunday and write our software scope.

- We would like to have weekly meetings at 7pm on Sundays.  Is that ok
with everyone?

---- 
E-mail sent to TA: 

Date: Mon, 30 Oct 2000 23:55:35 -0600 (CST)
From: Al Chu 
To: [email protected]
Subject: Web Based Gradebook - Questions


Hi, I am the group contact for web based gradebook.  We have some
questions that we were hoping you could answer for us.

1. What documents are we expected to produce for our project?  Because XP
has no established artifacts, we are a little confused on what to produce
(besides the obvious like user stories and unit tests).  Should we just
produce whatever we feel is necessary for us to produce (i.e. Software
Scope, flow diagrams, etc.)? Or do you the TAs have required documents for
us to produce?

2.  Since XP has no "hard-set" artifacts, what checkpoints are we supposed
to establish?  Are these checkpoints that we establish ourselves or with
you the TA?  (The webpage hints as thought the TA and the group selects
checkpoints together, but we are unsure).

3. Are we allowed to change roles of individuals within our group?  One
team member is a little busier than the rest and we feel it would be best
if someone else takes over the role of customer.

Thanks,
Al Chu

------
Received Reply from TA:

Date: Wed, 1 Nov 2000 13:07:22 -0600 (CST)
From: CS327 TA 
To: Al Chu 
Subject: Re: Web Based Gradebook - Questions


Hi,

3. You can change roles. Just notify me.

1. In terms of the artifacts, yes, XP doesn't require estabilished
artifacts. However, you need to submit artifacts that show how you
followed XP process. So in your case, user stories card, meeting
reports, or any logs to prove that you're doing pair programming would
be those artifacts to submit. There're no required artifacts. If you
used some kinds of diagrams to communicate among members, you can submit
those,too.

2. In terms of the milestone of the project, you can set your own
milestone based on the 'time cost' of user stories you are taking.
Put it up on the web, so that I can take a look at and give you comments.

Seung-won