• Leaving a clean project behind is an important goal for all teams. That means (at a minimum) that each team's second sprint should plan on

  • putting license information in source code,

  • writing team switch specifications for a guest build,

  • refactoring the wiki - in particular, deprecating some pages so that no one will waste time reading completely outdated material. But do leave some interesting history available.

  • planning to fix outstanding bugs.

• The spring presentation will take place during the third sprint, but teams may want to allocate time here for advance planning.

• Then, of course, there will be team specific deliverables.

Back to the CS682 home page.