You should not do a lot of writing for a status report (although in an eventful week several paragraphs in the Discussion section might be warranted); the goal is to provide a qualitative status update in addition to your quantitative data.
Status reports must be placed in the FogBugz wiki for your project. The status report is due the midnight prior to your scheduled meeting with your advisor. You should also bring a hard copy to the meeting.
A status report is not required in weeks that a cycle report is due.
Report identification: Course, Team designator and member names, Quarter (Fall, Winter, Spring), “Week N Status Report,” Day and Date Submitted; N is the MSOE quarter week during which the report is submitted.
Executive Summary: What are the key things that were accomplished during the last week? If there was exceptional variance or corrective action, also document it here. Be sure to include the actual results space permitting. For example, “We evaluated Java and C# as possible languages for implementation” doesn't say as much as “We selected Java as the implementation language.” The reader can read further if (s)he would like to know the rationale. Approximate length: 2-3 sentences
Status Update (a separate section for each member) including:
List of cases/subcases that were worked on in the past week.
List of cases/subcases planned for the previous week but that were not worked on (if any).
List of any new cases/subcases added in the previous week (if any), along with a brief summary of why.
List of any abandoned cases/subcases added in the previous week (if any), along with a brief summary of why.
For each case, include:
The case # and title hyperlinked to actual case.
Status (closed, in progress, not begun, abandoned).
Actual effort (time spent) vs. estimated for the week (actual time should match FogBugz logs).
Cumulative project effort for this cycle - previous total added to effort this period equals new total.
List of issues encountered in the previous week.
List of concerns and/or newly identified risks.
Discussion: Summarize key meetings, findings, successes, and risk updates. Approximate length: variable depending upon need: 1-6 paragraphs – use subsections if warranted
Plan Update (a separate section for each member) including:
Conclusion: Briefly summarize how you will you be moving forward in the next week (key priorities, etc.). Approximate length: Typically 1 sentence, but never more than 3.