Skip to Content

CS371 Sprint Grading Rubric (maybe CS581 too)

Posted on 2 mins read

This page contains the rubrics that the TA will use to evaluate team performance for each sprint. Sprint grades are not based on how much functionality you completed but rather how well your team is following some software engineering practices. (Yes, product quality and functionality will matter when it comes to final project grading, but the purpose of your project is also to learn and use good software development practices.)

Sprint 1

  1. Issues have been created that capture work being and to be done
  2. Issues have a Fibonacci story point value in their title
  3. Issues have been assigned to at most two team members
  4. Milestones have been created for each sprint
  5. Wiki home page, user story page, project overview page, and sprints page have appropriate initial content
  6. Initial working product has been demonstrated.
  7. GitHub repository is up to date with initial working product

Intermediate sprints

  1. Issues have been created and updated that capture work being and to be done
  2. Issues have a Fibonacci story point value in their title
  3. Issues have been assigned to at most two team members
  4. Sprint wiki page has been updated by day 3 with completion of prior sprint info and initial current sprint info
  5. Sprint issues have been selected by day 3 and assigned to the sprint milestone
  6. Work is being done on development branches, not on main; pull requests are being used to merge. (beginning late in sprint 2)
  7. Commits have issue numbers in their description, with hashtags
  8. All team members have contributed some code
  9. All team members have contributed some documentation
  10. Documentation appropriate to the sprint has been created/updated
  11. Increment of working product has been demonstrated
  12. GitHub repository is up to date with initial working product on main branch

Final sprint

  1. All of the points for intermediate sprints apply to the final sprint
  2. Final product has been demonstrated
  3. A “Status” note has been added to each user story on the user stories page, stating the level of completion of that user story
  4. A “Status” note has been added to the software design page stating how well the final product follows the described design
  5. Wiki pages are all updated to be in the final documentation state
  6. All issues that have been completed are closed
  7. All issues that have not been completed are left open and have a comment added that documents their status
  8. Final demonstrated product is based on the main branch in the Git repository