TA Resources: Studio Summary Grading


Solutions will be posted to GitHub:

  1. Go to IoT GitHub Organization
  2. Search for studio-XX-solution for some value of XX (Ex: studio-03-solution).


The studio summaries are intended to be a dialog with students. It’s an opportunity for us to:

As you review students’ work, please try to keep in mind that the goal here is enhancing their learning via great feedback (not “assessing” their understanding).

Give Personal Feedback!!!

When reviewing be sure that ever group gets some kind of personalized feedback. It would be best to give some sort of acknowledgment of good/bad on most changes, but that may be excessive in many studios. Be sure that some aspect of each groups work has something more than just cursory good/bad feedback.

It should go without saying that you should be reasonably professional, but


Most Studios will have:

Suggested Workflow

Do a Survey of Solutions

You will be provided with a “key” for all assignments, but large classes are a fantastic opportunity to crowdsource good ideas. Often there are great insights, suggestions, or solutions that weren’t obvious when the solution was written. In addition, there are often common errors and oversights that can be given a common response.

Before grading in earnest, do a quick survey of several different groups work. See if there are any things that stand out. This could save a lot of back-and-forth adjustments later. Feel free to share great insights among groups (but never directly share student work).

Review Approaches

Order: Question-by-question or Group-by-group

Some people prefer grading a single question for all groups, then the next question for all groups, etc. Others prefer to grade all of a single group’s work, then the next group, etc. Use whichever you are most comfortable with, but it’s best if you don’t commit any work until you are completely done grading all questions for all groups (see below on committing). This gives you a chance to go back-and-forth as necessary to ensure that you are being consistent and aren’t overlooking anything significant.

Consistency: Keep Common Responses

It’s often helpful to open a text editor and keep a log of common responses or particularly long responses that you may need to give to many groups. Then just copy/paste the response when needed (and possibly edit a little).

Process Overview

The basic process will involve:

  1. Open each group’s Repository (open a tab for each)
  2. Create a tag/release/branch on the original files for each repository.
    • Hopefully we can automate this or ensure that the initial distribution already contains these tags in future work.
  3. Create a “Pull Request” that compares the final submission to the originals.
  4. Use the “files” tab in the pull request to get a list of all the changes/additions to the files. Add comments / feedback.
  5. When done with all questions for all groups, commit each.

Grading Process Details

  1. Go to GitHub Classroom: https://classroom.github.com/classrooms/35315329-iot-sp18

  2. Select the link to the relevant studio.

  3. Open all Repos in tabs:
    GitHub Grading Open Repos

  4. If there isn’t already a tag/release, do the following in each:
    1. Click on the Commit link
      GitHub Grading Commits

    2. Select the Browse the Repository at this Point button for the most recent “bsiever” commit.
      GitHub Grading Base Commit

    3. Click on the Tree dropdown and enter the name original to create a branch.
      GitHub Grading Base Commit

    4. Close all repos when done and then re-open them via the submit link before the next step.

  5. Click on the New Pull Request button.
    GitHub Grading Pull Request

  6. The last commit before the deadline will already be selected. Select the original branch to compare to it.
    GitHub Grading Pull Request

  7. Enter the name Feedback and click on Create pull request.
    GitHub Grading Final Create Pull Request

  8. Click on the Files changed tab.
    GitHub Grading Files Changed

  9. Student additions will be shown with green bars. Removals/changes will be shown with red bars. To give feedback on any particular item move to the line number and select the “+” that appears:
    GitHub Grading Pull Request

    • Be careful of “skipped” work, which won’t be shown at all.

    • Markdown files also have a Rich Diff mode. This may help you read work when there is a lot of formatting (tables, images, etc.)
      GitHub Grading Rich Diff

  10. Add desired feedback. Be sure to use Start a review (or Add Review Comment if a review is already started) (NOT Add single comment nor Finish your review)
    GitHub Grading Comments

  11. When done with all feed back on all submissions click on Review changes dropdown, then enter the credit and/or description if there are lost points (only if huge omissions) in the comment box, enter the grade in the PowerApp Form but be sure to only enter grades for students who were present for the studio (check the studio grades) (If they completed the process/Roles.md file the names will show up in the review), then click Submit review
    GitHub Grading Pull Request