M1 Project Progress and Quality

• Instructions
• Grading Rubric

Instructions

Key Progress Criteria

• Overall Progress Consistent with Individual Expectations. The total number of features implemented and pull requests merged for Milestone M1 is consistent with the expected iteration effort (10 hours of coding work per team member).
• Unmerged PRs Don’t Count. Note that unmerged pull requests do not count toward the team’s progress.

Key Quality Criteria

• High-Quality Features. The features produced are of high quality:
  • They work correctly.
  • They have good ease-of-use (usability).
  • They have good look and feel (style).
• High-Quality Code. The code produced is of high quality:
  • The code follows style guidelines, including naming conventions and indentation.
  • The code is clean, neat, and easily understood.

Grading Rubric

• High-Pass:
  • Progress is deemed to solidly meet or exceed expectations.
  • Quality criteria are generally met, with only a few violations.
• Low-Pass:
  • Progress is deemed to be borderline, barely meeting expectations.
  • Quality is borderline, with a moderate number of features/code artifacts containing noticeable violations of the quality criteria.
• Fail:
  • Fails to meet requirements for Low-Pass.
  • Progress fails to meet expectations.
  • There are substantial violations of the quality criteria.