Tuesday, 2/23, 3:45 PM
Yesterday: work on Milton Bordwin's guest lecture, code review stuff
Today: nothing (other than class)

Monday 2/22, 8:30 AM
Yesterday: reread Cathedral and the Bazaar, visit team google code sites
Today: plan class for tomorrow

Sunday 2/21, 11:30 AM
Yesterday: nothing, as planned
Today: reread Cathedral and the Bazaar, visit team google code sites.

Saturday 2/20, 8:30 AM
Yesterday: nothing, as planned
Today: (or tomorrow) - reread Cathedral and the Bazaar

Friday 2/19, 9:00 AM
Yesterday: corresponded with Matt Passell and Jean-do about guest gigs. Didn't enter scrum report!
Today: nothing planned

Thursday 2/18
Yesterday:
Today:

Wednesday 2/17, 3:30 PM
Yesterday: updated code review and second sprint pages, printed material for Thursday guest lecture
Today: assign reading and writing for Tuesday

Tuesday 2/16, 1:00 PM
Yesterday: nothing
Today: check wikis, plan spring presentation, start code review docs

Monday 2/15, 10:00 AM
Yesterday: vacation
Today: check wikis, plan spring presentation

Friday, Saturday, Sunday
Yesterday: visited wikis, entered TBS convex hull idea, worked on guest speakers
Today, tomorrow, Sunday - family vacation time

Thursday 2/11: 10:30 AM
Yesterday: A little work on guest speakers.
Today: Visit wikis. Start second sprint specs.

Wednesday 2/10, 3:30 PM
Yesterday: visited wikis, prepared class, a little guest speaker stuff
Today: Guest speaker stuff (Adam, Donna)

Tuesday 2/9, 8:00 AM
Yesterday: nothing
Today: Prepare class, work on team switch specs, visit wikis

Monday 2/8 - a washout. I didn't even write a scrum report saying it was a washout. (I did do lots of other work to earn my state salary, but nothing for this course.)
Yesterday:
Today:

Sunday 2/7 9:25 AM.
Yesterday: No posting. Friday I worked on Milton Bordwin and Jeff Fried visits.
Today: Look at wikis.

Friday 2/5 9:35 AM.
Yesterday: finished scrum rules, firmed up Jean-do visit
Today: follow up Milton Bordwin visit, touch code review page, enter TBS enhancement issue

2/4 10:30 AM.
Yesterday: updated spring schedule, this file (my scrum schedule), met deadline for draft of presentation specs and scrum rule specs, email with Jean-do about guest lecture.
Today: Start code review page for Jean-do (not even on my schedule), check wikis - add comments. Fix spelling errors on See3PO wiki.

• Description. Implement scrum. For details, see the scrum rules.

• Why now? If we're going to use this methodology we need to start right away.

• Time estimate. One hour of class time per week. Two hours of my time writing and revising the scrum specs.

• Testing. We'll know my part is done when the scrums start.

• Whose job? Preparing the rules is my job. Following them is everyone's

• Partial deliverables. A working draft of the scrum rules must be ready in time for the class to prepare for the first scrum, to be scheduled for Thursday, Feb 11, after Adam's talk. So the deadline for this draft is Tuesday, Feb 9.

• Risk of failure. Very low. I've already started the task.
• Progress report February 3. Updated scrum rules based on the discussion in class yesterday - we should be able to settle on the draft there (with modifications) after class tomorrow.

• Description. Flesh out schedule for the part of the course work not covered by the team sprints:
  1. Specify format, audience, dates for the presentation.
  2. Specify how the "team switch" delegation will work, in time for review by class before we start.
  3. Preliminary information about poster and parties at the end of the semester.

• Why now? These later deliverables don't happen in the first sprint but they need to be scheduled now so that planning for the second sprint can take them into account.

• Time estimate. About four hours of my time.

• Testing. The test that proves these have happened is that the information appears on the course web page.

• Whose job? Mine, with feedback from the class.

• Partial deliverables.
  1. Thursday 2/4
  2. Thursday 2/11
  3. Draft Thursday 2/18, final 3/2 (end of sprint)

• Risk of failure. This will only happen if I don't do my job. There are no technical obstacles.

• Description. Arrange guest lectures.

  For each speaker:

  • Contact
  • Schedule dates
  • Arrange for readings in preparation, followup responses

• Why now? Not necessarily complete in first sprint. Two speakers already scheduled

• Time estimate. Two hours/week?

• Testing. The proof that this task is done is the appearance of the speaker.

• Whose job? Mine.

• Partial deliverables. Four more potential speakers contacted; negotiations underway. I can't put down dates here yet.

• Risk of failure. If a few of the people I hope to get can't come that will be too bad. It's unlikely that many will say no.
• Progress report February 3.
  Conveyed class preferences to Adam Leffert.
  Ellen Glusman all set for her talk.
  Jean-do Sifantus will do code review on March 2.
  Jeff Fried set for coding at Microsoft, some time in March.
  Milton Bordwin - negotiations underway.
  Jean-do Sifantus, Jeff Fried, Donna Ferullo set, Milton Bordwin almost set.

• Description. Provide regular feedback to teams by monitoring project wikis (personally, and publicly in class), writing Professor's comments. (The public scrums will help a lot with this too.)

• Why now? Not just now, ongoing.

• Time estimate. Two or three hours per week.

• Testing. You see it when it happens.

• Whose job? Mine.

• Partial deliverables. Professor's comments at least once/week.

• Risk of failure. Low.