Due: every Saturday by 11:59 pm. One report per person, plus one for the team.
Each team member must post an individual status report. The post title must be “<Name>’s Status Report for <due date>” (this helps the TAs and Faculty find and sort the reports).
A combined post will update the status of the project as a whole. This post title must be “Team Status Report for <due date>”.
All status report postings, individual and combined, should have a tag (i.e. tag in
wordpress) of “status report.” Add whatever other tags you wish.
In addition, each post should be assigned a category (i.e. a category in WordPress) with names “<Name>’s Status Reports” and “Team Status Reports”. These categories can then be displayed in a sidebar on your website, making it easy for you and others to find a specific set of reports.
Each team member should be participating in the status update every week. The
content will help you reflect on your week’s work and how that progress fits into the semester long schedule, as well as help the course staff understand what you will be working on in a given week. We will be asking about the progress of any deliverables during the week, and expect to see them completed by the following status report; if they are not completed, discuss steps to get back on schedule going forward.
Each team member must post an individual status report. The post title must be “<Name>’s Status Report for <due date>” (this helps the TAs and Faculty find and sort the reports).
A combined post will update the status of the project as a whole. This post title must be “Team Status Report for <due date>”.
All status report postings, individual and combined, should have a tag (i.e. tag in
wordpress) of “status report.” Add whatever other tags you wish.
In addition, each post should be assigned a category (i.e. a category in WordPress) with names “<Name>’s Status Reports” and “Team Status Reports”. These categories can then be displayed in a sidebar on your website, making it easy for you and others to find a specific set of reports.
Each team member should be participating in the status update every week. The
content will help you reflect on your week’s work and how that progress fits into the semester long schedule, as well as help the course staff understand what you will be working on in a given week. We will be asking about the progress of any deliverables during the week, and expect to see them completed by the following status report; if they are not completed, discuss steps to get back on schedule going forward.
Below are some questions to prompt the content of your status reports. and each question should be addressed. Each team member should be answering all of the following questions.
• What did you personally accomplish this week on the project? Give files or
photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).
• Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?
• What deliverables do you hope to complete in the next week? The whole team should answer the following questions in the Team Status Report:
• What are the most significant risks that could jeopardize the success of the
project? How are these risks being managed? What contingency plans are ready?
• Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?
• Provide an updated schedule if changes have occurred.
• This is also the place to put some photos of your progress or to brag about a component you got working.
Additional Week–specific status report questions will be Announced on Canvas.
While most of these are individual, there are occasional questions that require the whole team to discuss and include in Team Status Report.
• What did you personally accomplish this week on the project? Give files or
photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).
• Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?
• What deliverables do you hope to complete in the next week? The whole team should answer the following questions in the Team Status Report:
• What are the most significant risks that could jeopardize the success of the
project? How are these risks being managed? What contingency plans are ready?
• Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?
• Provide an updated schedule if changes have occurred.
• This is also the place to put some photos of your progress or to brag about a component you got working.
Additional Week–specific status report questions will be Announced on Canvas.
While most of these are individual, there are occasional questions that require the whole team to discuss and include in Team Status Report.