P2: Weekly Updates #
Deadline: the first Monday at 11:59pm Eastern Time following the week, for weeks 4-6, 8-12.
| Week | Date |
|---|---|
| 4 | Feb 02 Mon |
| 5 | Feb 09 Mon |
| 6 | Feb 23 Mon |
| 8 | Mar 02 Mon |
| 9 | Mar 09 Mon |
| 10 | Mar 16 Mon |
| 11 | Mar 23 Mon |
| 12 | Mar 30 Mon |
Requirements #
Each week, you should submit a brief update on your project, in the form of a plain text document (with markdown-style formatting). Your update should include a list of tasks done during the week, and pointers to the relevant artifacts (e.g., code, requirement documents, meeting minutes, etc.) as the outcome of the tasks.
Each week’s update won’t due until the following week’s Monday. You can decide which day during the week to submit your update, so that it is in sync with your team’s meeting schedule (for example, if your team meets every Tuesday, you can note down a todo list for the week during the meeting, and by next Monday, you can check the finished items in the todo list and submit that as the update). Please specify the date range of your update in the beginning of your document.
Here is an example weekly update illustrating the format:
# Project X Week 4 Update
Jan 26 - Feb 1
- [All members] discussed the project requirements and high-level architecture; [meeting minutes](LINK HERE e.g., https://github.com/pengyunie/project-x/blob/main/docs/meetings/week-4.md)
- [Pengyu, Bihui] setup Android project codebase structure; [commit/PR](LINK HERE e.g., https://github.com/pengyunie/project-x/commit/1234567890)
- wrote project proposal, where:
- [Liliana] wrote initial draft and project requirements
- [Larry] drew use case diagram
- [Saarang] wrote user scenarios and human values
- [Larry] drafted high-level component diagram for the project; [diagram](LINK HERE)
Submission #
Submit the update (in plain text) on Learn > Submit > Dropbox > P2: Weekly Updates - W[4/5/6/8/9/10/11/12].
Grading Rubric #
You will get the point as long as it is submitted on time and following the required format.
As for the content of the update, there is no direct impact on the grade at this point, but we may reference to them when deciding the individual scaling factors.
Feedback #
The weekly updates is a perfect opportunity for you to get timely feedback on your project from the course staff!
You will usually see a reply on Learn from the course staff within 48 hours of your submission. If you are making good progress and everything looks right, our feedback might be as simple as LGTM (Looks Good To Me). If you are facing some issues, feel free to mention that in this weekly update and we will try to help (providing suggestions, schedule some time for discussion, etc.).