• Tuesday January 26

    Where we've been, where we're going.

    Scrum projects make progress in a series of sprints, which are timeboxed iterations no more than a month long. At the start of a sprint, team members commit to delivering some number of features that were listed on the project.s product backlog. At the end of the sprint, these features are done--they are coded, tested, and integrated into the evolving product or system. At the end of the sprint a sprint review is conducted during which the team demonstrates the new functionality to the product owner and other interested stakeholders who provide feedback that could influence the next sprint.

    Scrum at Mountain Goat Software.
    Scrum at wikipedia.

  • Thursday, January 28

    writing assignment for first sprint.

  • Friday, January 29

    Professor's first sprint schedule posted.

  • Tuesday, February 2.

    Team spring schedule drafts due. Note various deliverables specified below - these need to appear. The detailed functionality for the February sprint (due March 2) must be part of this schedule.

    In order to make sure that schedules are current and appropriately detailed, I will require that all coding stop any time I find your schedule out of date, to resume only when I have (re)approved it.

    Short discussion of topics the class would like next week's guest speaker to address. Here are his suggestions.

    Discussion of how we will run our (not) daily scrums.

    Note after class: the draft schedules were essentially final, and have been approved. So the rest of the schedule advances.

  • Thursday, February 4.

    Dan Phillips (briefly) at 4:00.

    Work on draft of scrumRules.html.

    Team meetings.

  • Tuesday, February 9.

    Team progress reports (VisitME second deliverable, See3PO camera saga, TBS unit testing)

    Team meetings.

  • Thursday, February 11.

    4:00 Team meetings.

    5:30 Guest speaker: Adam Leffert

  • Tuesday, February 16,

  • Thursday, February 18.

    Team meetings 4-5:00.

    5:15. Guest speaker: Ellen Glusman: Software Quality Assurance

  • Tuesday, February 23.

    Discuss The Cathedral and the Bazaar .

  • Thursday, February 25. Discuss code review.

  • Tuesday, March 2.

    First sprint release. Brief reports from each team, including live See3PO demo.

    Discuss deliverables for the second sprint.

  • Thursday, March 4.

    5:30. (rescheduled) guest speaker: Jean-do Sifantus on code review.

  • Tuesday, March 9.

    Discuss/approve schedules for second sprint, including team switch information.

  • Thursday, March 11.

    5:00. Guest speaker: Milton Bordwin, Campus Center room 2550B.

    Spring break

  • Tuesday, March 23

    Documentation for guest builds ready.

  • Thursday, March 25.

    Team switch exercise.

  • Tuesday, March 30.

  • Thursday, April 1.

    Second sprint release date.

    Guest speaker Donna Ferullo, 5:30-6:45. Here are her slides.

    Project Management Lessons Learned: Adventures in Technical Clinical and Research Software Projects.

  • Tuesday, April 6.

    Draft specifications for third (final) sprint.

  • Thursday, April 8.

    Spec for final sprint due.

  • Tuesday, April 13.

    Guest speaker: Jeff Fried - software development at Microsoft. Preliminary reading from David Gristwood.

  • Thursday, April 15.

  • Tuesday, April 20

    Spring presentations. Specifications to be announced.

  • Thursday, April 22.

    Presentation feedback.

  • Tuesday, April 27.

    5:30. guest speaker: Jean-do Sifantus on code review Part II

  • Thursday, April 29.

    code review: looking at source from each of the projects.

  • Tuesday, May 4.

    Final release. Functionality freeze!

    Poster draft due (we'll comment on each others')

  • Thursday, May 6

    Dry run of setup for alumni event.

  • Tuesday, May 11.

    Final release. Final draft of poster. Final report from teams. Bug list clean.

  • Wednesday, May 19

    Poster session at Department annual alumni event.