Status Report

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

Weekly status reports help to keep your boss, the executives, the customers, and yourselves informed about your progress. It ensures that you understand your problems, notice if you are unproductive, and get help.

Just like in a real software development project, each week

• You will send an individual status update to your team each week. This usually fits on a page. Every team member should read every individual status report, before the weekly team meeting.
• Your team will provide a team status update to management each week. This must fit on a single page.

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. (It can be empty for the first .)
• The second section should report the progress you've made this week: what you've done, what worked, what you learned, where you had trouble, and where you are stuck.
• The third section should outline your plans and goals for the following week (including, in the team report, 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, so that you don't think just about the next week.
• Team reports should have a fourth section: an agenda for the meeting with your TA.

You might 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 team's git repository should contain a top-level directory called reports, with subdirectories named week1, week2, ..., week11. Your group should (in your documentation and every other respect) pretend that these directories do not exist — they are for the convenience of the course staff.

You will commit your individual status reports to the appropriate directory with a filename of uwnetid.txt. Your team status report will appear in a file named team.txt. Neither team nor individual status reports are required for the first week of the project.