Grading

Regular Projects

The structure and metrics of the grading for each Project is described below and the possible grades for each item are indicated using [square brackets and italics]. 

• Design Research Modules & Coding Research Modules [0 to 10, each]
  • Design and Codings Research Modules are assessed separately but follow the same structure, described as follows
  • Each Research Subject needs to correspond to a Subject Assessment Application (SAA), which in turn needs to receive 1 positive feedback (“pass” vote) from a peer to be considered “done”
  • In case a SAA gets a negative feedback (“no pass” vote), the related Subject requires a revision and the submission of a new SAA.
    • While correcting a SAA the evaluator should halt as soon as a breaking/careless mistake is found and return it with a “no pass” vote
  • Each student must correct at least 1 SAA per Subject
  • In order to be able to correct a SAA a student needs to have handed in an application for that same subject beforehand
  • If necessary an Instructor can evaluate SAAs (e.g. if it takes too long for a student to be able to do so)
  • The grade for each Research Module consists of the average of the following topics:
    • 60% - Pass votes [0 or 10]
    • 30% - Average of the grade given for “quality of feedbacks” made [0 to 10]
      • Each feedback can be assessed as Not useful (0), Useful (6) and Very useful (10)
    • 10% - Completion of all necessary feedbacks (1 per Subject) [0 or 10]
• Product Development
• This grade consists of the average of the following topics [0 to 10]
  • 10% - Delivery to Inna of all related files via Github or similar digital mean [0 or 10]
  • 65% - Average of grades given by a group of industry professionals, related to the presentation and demonstration of the finished Product [0 to 10]
  • 25% - Jafningjamat is a way that the group’s members can assess each other’s participation during the work. This grade is the average of all received evaluations [0 to 10]
• Extra points
  • An extra 0.1 point is added to the final grade of a Project for any of the following items:
    • TODO

Special Projects

Some projects do not fit in this grading structure, which is why they have their own, as can be seen below.

Project 2

The students are asked to spend 30h on different activities related to understanding the web development field of work better and to start integrating in the community. Examples of what these activities could be are:

• Participation in related events and conferences, both as speakers/instructors and organization team
• Publication of related articles
• Visits to/Interviews with related institutions

The guidelines to construct the final grade are:

• A report of hours spent (containing detailed description of activities and outcomes) should be created and delivered in Inna
• The final grade is the average of all points received for the hours spent [0 to 10]
• Each non-spent hour is given 0 point
• Each hour spent gets a grade [0 if out of scope or 10 if within scope]
  • A validation of the activities as being within the scope of the Project is made by the instructors
  • If in doubt as of an activity would be counted as “within scope”, the student should refer to the instructors to make sure
• No activity in the report should account for more than 6h (even if it took longer)

Project 7

The students are asked to explore one or more topics that they consider will be part of the future of web development, as opposed to currently popular topics. The final grade is the average of the grades given to these following parts. [0 to 10]

Research (50%) [0 to 10]

The student must create an article detailing their research with at least 1500 words. A group of industry professionals and peers will read through it and give it a 0 to 10 grade for the quality of the work.

Project (50%) [0 to 10]

A Product must be created to demonstrate the research topic and, similarly to what happens in regular Projects, the grade will be composed of the average of the following topics:

• 10% - Delivery to Inna of all related files via Github or similar digital mean [0 or 10]
• 65% - Average of grades given by a group of industry professionals, related to the presentation and demonstration of the finished Product [0 to 10]
• 25% - Jafningjamat is a way that the group’s members can assess each other’s participation during the work. This grade is the average of all received evaluations [0 to 10]

Project 8

• TODO

Cyclical Presentation Seminars

Every semester there are 3 Presentation Seminars with the participation of industry professionals who help in evaluating the students’ work. These seminars last for 3h and count on enough time slots for 6 presentations of 20-25 minutes.

It is the responsibility of each Group to apply for a specific Seminar to present their Project’s results. If a Seminar’s agenda is full upon a Group’s application it will be necessary to wait until the next one.

The instructors can rearrange the priority of presentations in the 

Seminars

 to avoid that some students present more than others.