Progress Document Grading Rubric

The progress document should summarize the work that each team member completed in the previous week.

Requirements

A completed template submitted to Canvas by the specified deadline.

Logistics and Timing

The progress report is due at midnight on the day before the mentor meeting.

Grading

Grades are assigned on a scale of 0-5 points individually to each student. In Canvas this is set as a group assignment, but with individual grades. I strongly recommend using the Canvas SpeedGrader and filtering by project group on the grade book page.

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 meeting” mindset. Students will use getting stuck as an excuse to not finish their work. Students having issues should raise those issues ahead of time.

Mentors may apply additional grading standards to the rubrics below.

Grade	Description
5	All information filled out, task information is descriptive, complete, and easy to follow. The write-up is readable and understandable with consistent formatting and style across all write-ups. 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 (proper PR attached to it and complies with any project standards around coding and reporting) and can be run / reproduced with little effort.
4	All information filled out, task information is descriptive, mostly complete, and relatively easy to follow. Write-ups may have minor presentation issues (grammar / inconsistent style or formatting) which only mildly affects its 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 (proper PR attached to it and complies with any project standards around coding and reporting) and can be run / reproduced, but requires changing a few lines.
3	All information present, but the task description has presentation issues which affect its readability (grammar / inconsistent style or formatting). 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 student in order to obtain or reproduce. Student got "stuck" on an area and raised the concern during the mentor meeting, rather than beforehand.
2	Missing information, significant presentation, and content issues. Work incomplete.
1	Incomplete and demonstrates a lack of effort.
0	Zero effort / not submitted

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.