Weekly Report Grading Rubric

The weekly report summarizes the work that each team member completed in the previous week. It is posted as a comment on each of last week’s GitHub issues, following the weekly report template, alongside the code pushed to GitHub.

Requirements

Each student pushes their work to GitHub (code in an open pull request, reports in issue comments), comments on each of last week’s issues using the status format in the template, and posts a link to those comments in the weekly Slack thread for the project. While we encourage the use of LLMs for coding, these reports must be written entirely by the student.

Logistics and Timing

The weekly report is due at midnight on the day before the mentor session.

Grading

Grades are assigned on a scale of 0-5 points individually to each student. Grades are recorded individually for each student in Canvas; filtering the gradebook by project group makes this easier.

Three points of emphasis:

1. Don’t fall behind on grading!
2. Make sure to establish standards early. Giving everyone a 5 for everything is going to encourage people to slack; make sure that the high performers are rewarded and people who are slacking know that you are aware of their lack-of-effort.
3. Make sure to establish a “no new issues raised during the mentor session” mindset. Students will use getting stuck as an excuse to not finish their work. Students having issues should raise those issues ahead of time, with their TA or in the project Slack channel.

Mentors may apply additional grading standards to the rubric below.

Grade	Description
5	A report comment is posted on every issue and linked in the Slack thread. Every piece of acceptance criteria has an accurate status and a descriptive, complete, easy-to-follow note. The write-up is readable and understandable with consistent formatting and style. Student demonstrated significant effort over the course of the week and did not procrastinate or reach out for assistance in an untimely manner. Any code produced is conveniently shared (a proper pull request linked from the issue that complies with project coding standards) and can be run / reproduced with little effort.
4	A report comment is posted on every issue and linked in the Slack thread, and the notes are descriptive, mostly complete, and relatively easy to follow. Write-ups may have minor presentation issues (grammar / inconsistent style or formatting) which only mildly affect readability. Student demonstrated significant effort over the course of the week and did not procrastinate their work or reach out for assistance in an untimely manner. Any code produced is conveniently shared (a proper pull request linked from the issue that complies with project coding standards) and can be run / reproduced, but requires changing a few lines.
3	All report comments present, but the notes have presentation issues which affect readability (grammar / inconsistent style or formatting), or the reported statuses don't match what is actually on GitHub. Student did not complete their work due to planning (procrastination) or not getting in touch with the TA or Mentor in a timely manner. Any code produced requires back-and-forth with the student in order to obtain or reproduce. Student got "stuck" on an area and raised the concern during the mentor session, rather than beforehand. Student is not attending meetings on time, is not contributing their fair share of the work, is not responding to TA review comments, or is otherwise not meeting expectations for effort and participation.
2	Missing information (for example, missing report comments or no Slack link), significant presentation, and content issues. Work incomplete.
1	Incomplete and demonstrates a lack of effort.
0	Zero effort / not submitted. No comment has been made to the issues describing tasks. Automatic 0: a task required code and no code was pushed to GitHub.

Late Policy

Late submissions made within 24 hours of the deadline will automatically be docked two points. Submissions after that time will receive a grade of zero. Comment, push, and Slack post timestamps (as shown on GitHub and Slack) are used to determine whether a submission is late.