Previous Iteration Wrapup

• Clearly post what user stories were accepted by the customer, which were dropped, and which were deferred to a future iteration
• Ensure that meeting minutes from your final iteration customer meeting are posted to your team wiki
• Ensure your task actual times are posted in Rally (or equivalent), post your task/time report to your team wiki and notify Dr. Janzen

Iteration Planning

• Clearly post what user stories were accepted by the team to complete in this iteration, and which were identified as stretch goals
• For each accepted user story, document customer acceptance tests on the course wiki
• Create new iteration with user stories, tasks, task owners, and time estimates in Rally (or equivalent)
• Set intermediate internal deadlines as appropriate

Mid-Iteration Review

• Post any artifact to be reviewed on the course wiki by Thursday at 8am, notify Dr. Janzen by email when this is done

Iteration Completion

• Prepare to present completed user stories via customer acceptance tests
• Anticipate user stories to be completed in next iteration; do initial estimation analysis
• Post any artifacts to be reviewed in the iteration planning meeting on the course wiki by Thursday at 8am, notify Dr. Janzen by email when this is done
• Ensure that all artifacts and metrics from the previous iteration are posted to your team wiki
• Metrics should include the following at a minimum:
• test coverage (overall and by package)
• WMC (overall and by class)
• source lines of code (overall and by class)