Peer feedback guidelines for Project 2 (50% of project grade)

Provide feedback about the following topics:

  1. Is the purpose of the project communicated clearly?
  2. Is the source of the data made clear?
  3. Is the interpretation of figures clearly explained?
  4. Is the user interface explained adequately?

Keep in mind the qualities of good feedback (as described in the rubric for project 1).

Feedback should address the code organization (see Grader rubric below) and written communication. Help your classmates create a great portfolio.

Late project drafts will lose 25% of final grade (you need to upload your draft on time so that your peers can give you feedback). Late feedback will not receive a score. You may receive peer scores but they will not be recorded. Students who submit late feedback scores, or who fail to return feedback scores, will lose 10% per set of scores on their own project. Your peers need your scores for their final grades.

Feedback rubric (to be used in scoring the feedback you received from peers)

Points Description
7 Feedback was specific – you know exactly what to improve, and what you did well
6 Feedback was “meta” – the feedback went beyond finding typos to helping you with higher-level improvements (such as thinking about things from the audience’s perspective)
2 Feedback was respectful and optimistic – you feel helped and encouraged after reading the feedback

Grader rubric for Project 2 (50% of project grade)

Points Description
5 Code structured – code is on Github, includes a README, and a clear project structure
5 Code commented – code is commented and readily understood by the grader
10 Dashboard hosted on ShinyApps.io and works correctly