- we are all aware that assessment may be subjective in nature. In case of disagreement, the informed judgment of the Professor is the final decision.
- in the grading criteria presented below, the mandatory parts do not count as "yes" for grading.
- Presentation and demos are mandatory.
- In case of a task failure, the students receive instructions for repetition through Canvas
The concept: The students prepare a 7 minute presentation on a topic that is relevant to DevOps. All students in a presentation must be present and speak in a balanced manner.
| Yes | No | |
|---|---|---|
| timing: The presentation's length is between 6:30-7:30 minutes (hard limit) | Yes | No |
| well-structured: Structure is announced and graphically visible | Yes | No |
| motivation: The presentation contains a good, motivating introduction telling why this presentation is important | Yes | No |
| technical: The presentation contains one part that is deeply technical | Yes | No |
| code: The presentation contains valuable and readable code snippets | Yes | No |
| originality: The presentation contains one part that is original (eg less than 100 results on Google on this topic) | Yes | No |
| reflection: The presentation contains a reflective part | Yes | No |
| sota: There is one good slide positioning the presentation in the state of the art | Yes | No |
| take-home: The last slide contains a good and concise take-home message | Yes | No |
| loudly: The speakers talk loudly and clearly | Yes | No |
| engagement: The speakers engage with the audience | Yes | No |
| humour: The speakers are fun, have humour | Yes | No |
| readable-slides: The slides don't have too much text | Yes | No |
| illustration: The slides contain nice illustrations | Yes | No |
To pass, you need at least 8 "yes".
The concept: The students write an essay on a topic relevant to the course. Example of essays, see 2019 essays, 2020 essays
| Yes | No | |
|---|---|---|
| format: The essay is in PDF | Mandatory | - |
| length: The essay length is between 2400-2600 words, incl. references (hard limit) | Mandatory | - |
| relevant: The essay addresses a topic that is relevant for DevOps | Mandatory | - |
| title: The essay has a good and focused title | Mandatory | - |
| generative AI: the essay contains "I/We certify that generative AI, incl. ChatGPT, has not been used to write this essay. Using generative AI without permission is considered academic misconduct." | Mandatory | - |
| well-structured: The essay is well structured | Yes | No |
| problem: The intro clearly states a relevant problem | Yes | No |
| sota: There is one part positioning the essay in the state of the art | Yes | No |
| conclusion: The conclusion contains an emphasized key take-away of the essay | Yes | No |
| self-contained: The essay is self-contained, one can understand it without reading something else (expected knowledge of the reader: a master student in computer science) | Yes | No |
| innovative: The essay contains innovative ideas or material | Yes | No |
| figures: The essay contains relevant and informative figures | Yes | No |
| listings: The essay contains relevant and informative listings | Yes | No |
| sound: The essay is sound, factual, and accurate | Yes | No |
| references: The essay contains references, appropriate in number and quality (10 good refs is a minimum, incl. at least 3 academic references) | Yes | No |
| elegant: The essay presentation is elegant and visually appealing (eg LaTeX, InDesign) | Yes | No |
| reflection: The essay contains a reflective part | Yes | No |
To pass, you need at least 8 "yes".
The concept: Students prepare a demonstration involving DevOps technology, to be performed during the lecture. For example, a demo typically involves multiple virtual machines, likely deployed in the cloud. A demonstration is scripted, prepared and lasts 6:30-7:30 minutes.
| Yes | No | |
|---|---|---|
| timing: The demo lasts between 6:30-7:30 minutes (hard limit) | Mandatory | - |
| relevant: The demonstration is clearly motivated (why it matters for Devops?) | Yes | No |
| narrative: The demo contains a good narrative | Yes | No |
| difficulty: The demonstration is difficult to do | Yes | No |
| speech: The demo is accompanied by a clearly and structured speech | Yes | no |
| originality: The demonstration is original (there are few demos/tutos on this topic on the Internet) | Yes | No |
| aesthetics: The demo is visually appealing | Yes | No |
| easter-egg: The demo contains an easter egg related to the demo topic | Yes | No |
| engagement: The speakers engage with the audience | Yes | No |
| liveness: The speakers update some code / config live | Yes | No |
| take-home: The demo includes a clear and visible take-home message | Yes | No |
To pass, you must have at least 8 "yes".
The concept: you contribute to one open-source project related to DevOps. Yout get at least one merged pull-request.
Criteria for the selection of the open-source project: 1) The project is related to DevOps 2) The project has more than 100 Commits 3) The project has an active community on GitHub.
| Yes | No | |
|---|---|---|
| difficulty: The contribution is a difficult piece of engineering, either a bug fix or a new feature | Yes | No |
| workflow: The contribution is done per the best practices of open-source (declaration of intention, WIP, ready for review, conversation) | Yes | No |
| merge: The contribution is merged in the main branch of the target project. | Yes | No |
To pass, you must have 2 yes.
The concept: you create an executable tutorial about a specific technology related to Devops. You deliver your tutorial on a platform supporting execution, such as KillerKoda, mybinder.org, collab or equivalent.
| Yes | No | |
|---|---|---|
| no-account: The tutorial does not require to open complex or paying accounts for the grader. Secrets can be shared with the course GPG key | Mandatory | - |
| executable: The tutorial can be automatically executed from beginning to the end in the browser | Mandatory | - |
| ilo: The tutorial states the intended learning outcomes. | Mandatory | - |
| motivation: The tutorial is clearly motivated (why it matters for Devops?) | Yes | No |
| background: The tutorial gives enough background | Yes | No |
| illustrated: The tutorial is illustrated with an informative figure (eg a flowchart) | Yes | No |
| pedagogical: The tutorial is easy to follow | Yes | No |
| original: The tutorial is original, no or few similar tutorials exist on the web | Yes | No |
| easter-eggs: The tutorial contains an easter egg | Yes | No |
| language: The language is appropriate (structure, grammar, spelling) | Yes | No |
To pass, you must have the mandatory parts and at least 5 "yes".
The concept: you provide constructive and timely feeback about one task from categories "essay" and "executable tutorial". The feedback is provided in a written manner as a well-structured comment on the PR of the task.
| Yes | No | |
|---|---|---|
| substance: the feedback is substantiated (at least 500 words) | Mandatory | - |
| generative AI: the feeback contains "I/We certify that generative AI, incl. ChatGPT, has not been used to write this feedback. Using generative AI without permission is considered academic misconduct." | Mandatory | - |
| high-level: the feedback starts with a list of high-level strengths and high-level weaknesses about the work | Yes | No |
| timeliness: the feedback is provided 2 business days (48h) after the "go" from the authors | Yes | No |
| constructive: all feedback points are constructive and clearly actionable | Yes | No |
| structure: the feedback is well-structured (eg. along the outline of the work under feedback) | Yes | No |
| pointers: the feedback contains valuable pointers to additional material | Yes | No |
To pass, you must have at least 4 "yes".