>87.5: 1, >75: 2, >62.5 : 3, >50: 4, ≤50: 5
Please note that the above schema MAY be subject to a grading curve for individual tests or assignments.
| 50% | 2 presentations (the second being the final tryout before the official defense) |
| 25% | bi-weekly reviews |
| 25% | regular project documentation using appropriate tools (sprint board or kanban board) self-reliance |
Note that the above criteria contribute only to the practice part of the grade. The other half will be determined by the theory teacher. Both parts have to be positive in order to receive a positive grade.
The presentation should take exactly 8 minutes. For each full minute of deviation a full grade will be deducted. Please test your equipment in the actual room to make sure to have a swift transition or use the available computer.
The first person presenting should introduce the overall project goals and the team (who is who) for about two minutes as part of their presentation time. This part of the presentation must not be too technical and must not assume any prior knowledge. It may involve screenshots, photos, a video or a very short slideshow using your favorite presentation software.
Afterwards, about two minutes should be used to give a high level overview of the own contribution. This has to be done by each student. Again, it may involve screenshots, photos or a very short slideshow using your favorite presentation software.
The rest of the presentation (about 4 minutes for the first student, about 6 for subsequent students) should demonstrate working software, the development environment and give a good insight on what has been done as well as how it has been done. If the project involves hardware, you may show photos or videos to give a better impression. Finally, each student should also explain which major difficulties they faced and how these were solved before wrapping up their presentation.