flickr photo by mikefisher821 http://flickr.com/photos/grade6kms/5146468921 shared under a Creative Commons (BY-NC) license

Grading Rubric


Partial 1

  • 8:30am group: Friday September 8th
  • 10:00am group: Friday September 15th

Partial 2

  • 8:30am group: Friday October 20th
  • 10:00am group: Friday October 27th

Final Exam

  • Planned for 2 hours but you have up to 3 hours in the exam
  • 8:30am group: Tuesday November 28th
  • 10:00am group: Thursday November 30th


We really want to focus on learning as part of #Tec21 and this is how we are approaching grades in this class. We focus first on learning as an individual student with the instructor (and your fellow students) to help you on your learning path.

But we still need Partial and Final Grades!

Correct, each student will submit to the instructor (Ken) a portfolio of work with a requested grade (between 1 and 100). We will guide each other in that process with the knowledge that 70% (and above) is a “passing” grade allowing the student to continue to the next course in the series. In our first semester (Jan-May 2016) on this #AbolishGrading journey, we developed a rubric to help guide the students in this process and I will ask everyone for input on how to improve that rubric. Note that the danger of rubrics is that it can turn progress in “checkboxes” and we want to avoid that here.


The grade from your participation in i-Week (Semana-i) counts as 5% of your grade.

We will take your grade from this course and multiply by 0.95 and then add the points obtained from your i-Week activity.

If for any reason you are exempt from i-Week participation we will not apply that rule.

Our Rubric

Well, this is under construction as a group.

What do I need to do to pass this course?

You learn the list of concepts in the course (see the Mastery Topics in the menus at the top). The official course outline shows that and is reflected in the list of mastery topics for this course. In order to justify your grade (requested by student, authorized by instructor), you should track the following information on your blog, on GitHub, in other digital or paper format:

  • Knowledge acquisition (technical and experience).
  • Reflection through your blog, what did you learn each day and each week? What are your questions?
  • Helping others, track who you work with and on what. You can learn and teach each other.
  • Meetings with Ken (in class or out). You should track these and talk in person with the instructor (one-on-one and/or small group) at least once per week.
  • (possibly)Project throughout the semester (formal or informal, define a project to work on with a small team).
  • List of mastery items.The “topics” for the course.

CC BY-SA 4.0 Evaluation by Bauer Ken is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.