Status Report

Due: Individual status reports by every Sunday 23:00
Due: Team status reports by every Monday 23:00

Weekly status reports help to keep the executives, the customers, and yourselves informed about your progress. CSRocks is asking you to send them a brief team status update each week. Additionally, you will send an individual status update to your team each week. The team status update must fit on a single page, and most individual status updates will, too.

Each status update should have three sections. Each section is typically about the size of a paragraph, but it can be organized as bullet points or in some other clear way.

• The first section is easy. It should be an exact copy of the third section from last week — that is, your goals from a week ago. (The first week, it can be empty.)
• The second section should tell us about the progress you've made this week: what you've done, what worked, where you had trouble, and what you've learned.
• The third section should outline your plans and goals for the following week (including who is responsible). Bullet points are fine. If tasks from one week aren't yet complete, they should roll over into your tasks for the next week. It's good to include some less-detailed longer-range schedule items in this list as well.

You may find it helpful to read the more detailed instructions for writing a research status report from which the CSE 403 guidelines have been adapted.

Submission

Your individual status report should be available to your teammates and to the course staff. We recommend emailing them to your team mailing list, where they will show up in its archives, using a descriptive subject line so they can be easily found. You may use some other mechanism (such as committing them to your repository), but your team development webpage must indicate how to find them, and they should be timestamped. You must also submit them to the Catalyst dropbox.

Your team status report will be submitted using Catalyst dropbox.