KTH DevOps Course 2026 Edition
This repository contains the material and content of the DevOps course at KTH Royal Institute of Technology DD2482.
$ git clone ssh://github.com/KTH/devops-course/ --branch 2026 --single-branch
The schedule is at https://www.kth.se/social/course/DD2482/calendar/
If you can't see any schedule events on the HTML page
Change course rounds/groups in My settings or change the time period above so that it conforms to the course round.
Week 1 (26/8 13h-15h): Introduction (mandatory)
- Preparatory reading: DevOps principles and demo
- Course introduction by Larissa Schmid (Teaching philosophy, interactive classroom, Expectations, Team, Agenda, Grading, Communication, Infrastructure, Master's theses and Research)
- Goals: watch the repo, register one first task as a pull request on this repo.
- Seminar on 28/8 (09h-12h), 03/09 (09h-12h): Open schedule - discuss your goals for the course, your planned tasks, and any other questions you may have.
Week 7 (7/10 13h-15h): Other topics
To pass the course, the student has to complete and pass between 3 and 5 tasks:
- The tasks are in category: "demo (mandatory)", "scientific paper", "executable tutorial", "contribution to open-source", "feedback", "project" (project and demo are mandatory, at most one in the same category, it is not necessary to cover everything).
- The grading criteria page is the unique reference which explains how to pass each task category.
- The student proposes a category and a topic, which is discussed and accepted by the TA. The proposal is made as a structured pull-request on this repository. The 3-5 graded contributions must have little overlap.
- The same student cannot choose the same topic for two different tasks. The 3-5 tasks should cover different aspects of DevOps.
- Deadlines:
- Deadline for demos and paper presentations: the day and time they are given in person
- Deadline for tutorial and opensource: Sep 24, 23h59 Stockholm time
- Deadline for project: Oct 10, 23h59 Stockholm time
- Deadline for repeated tasks (all): Oct 27 2026, 17h Stockholm time.
- Deadline for feedback on tasks: 2 business days after the "go" from the authors
- Hand-in your async tasks via a new PR that updates your proposal document with a link to the artifact/contribution/feedback
- The deadlines are strict and cannot be extended. Not meeting a deadline means failing the task / the repetition.
- Final grading scheme
- E: 3 completed tasks (excluding feedback)
- C: 3 completed tasks + feedback
- B: 5 completed tasks
- A: 5 completed tasks + active participation in all but one seminars
- Active participation: attendance to all but one seminars between 10/09 and 14/10, a traceable record of questions asked during seminars (through GitHub issues) and the answers you received to them.
- Group work is mandatory (max 2 persons) but you cannot be with the same person for more than 2 individual tasks. You are not allowed to work alone. When you send a pull request for registration, please follow the name convention of using email addresses of two members to create the folder: email-email.
- A failed task requires to pass it again at the end of the course (repeat), based on the feedback from the failure. A task can only be repeated once.
- If the whole course is failed, no grades are kept if the student registers again to the course the year after.
- After a proposal has been merged, the topic of that proposal cannot be changed.
- All communication for the course DD2482 should be sent to dd2482@eecs.kth.se.
- you create issues here if you think the question is good to be discussed publicly, the rules of netiquette fully apply.
Lectures The lectures are held on campus (no hybrid / no video link). The lecture locations are given on KTH Social https://www.kth.se/social/course/DD2482/calendar/. The first lecture is mandatory, the other ones are strongly encouraged.
Seminar sessions
- Seminar slots are used to present and discuss the "demo" and "scientific paper" tasks. They are given in person and correspond to the weekly topics as outlined in the schedule.
- Seminar slots are not mandatory, but you have to be present to present the tasks you proposed.
- Active participation (and therefore attendance) in all but one seminars between 10/09 and 14/10, covering the topics of weeks 2 to 7, is required if you are aiming for an A.
Examinations: Some tasks require physical presence (demo, scientific paper), others do not (project, open-source, feedback).
- A software engineering course (eg DD2480)
- A networking course (eg IK2218)