VidhiKulkarni / teamlace

GNU General Public License v3.0
0 stars 0 forks source link

William Li - Review Ticket (Proctored MCQ Week2 : Quiz3 and Create Task review) #35

Open 3ghin5 opened 2 years ago

3ghin5 commented 2 years ago

Points

Scoring guidelines for crossover graders 4.5/5.0 maximum Establish your crossover pair early in the week, they can't be in your ASI activity. You need to know who you are scoring before ASI activity as you will be assisting in evaluations. 3 points, use bullets as indicated above, 1 point per sub-bullet 1 point, Participation: .20 for classroom presence and participation each day .5 point, Quality of work: grader should be looking at effort toward learning and understanding vs perfunctory bullet chasing (0, .25, .5) The last part of grading is providing point total, high points in crossover grading session, positives in work, and suggestions for future. Teacher evaluation, last .5 of 5 Reviewing work, providing feedback and obtaining inspiration from others work is a key skill in Computer Science. Seeing evidence of this in evaluation is critical to success in receiving credit from Teacher. Make sure when I am looking at your Ticket it is easy to find Ticket you evaluated. As an individual, I will be looking at how you follow canvas and cspcoders weekly posts. As an individual, I will always be evaluating your engagement and participation. Makeup Policy Coordinated makeup with Teacher requiring Tutorial is an option for any assignment, but makeup will not be calculated in initial scoring. If you miss classroom activity that awarded a point, you will receive a 0 for that activity.

aidanywu commented 2 years ago

4.25/4.5 Comments: Study plan not on GitHub Pages, 3c i in the written response contains two procedures instead of one.