2026 Course Plan
Important Info §1
This is a collection of the most important information.
We have lectures and group exercises in 358-067 and 358-068.
You can hand-in the exercises at DTU Learn
You can communicate with the TA and each other on Teams
The TA will be available on days without presentations in the exercise rooms between 13:00-15:00.
Day By Day §2
28/05 Groups Are Made Public G0
Today the groups are made public.
08/06 First Day L1
On the first day, we first meet for a brief introduction to the course. Before today, please:
Create a Group Contract with your groups.
Please have created a GBar Gitlab user (see Gitlab (§4)).
In the beginning of the lecture the user-stories are made available and you get to ask questions to the customer to get an idea of their priorities.
After the lecture, will all groups with a group contract will get assigned the Gitlab project, which you should develop on from here on.
10/06 First Customer Meeting M1
In the first customer meeting, you will have to present your plan for what you will have done by 2026 Course Plan (M2).
Every group will have 15 minutes to present and ask for feedback (see 2026 Course Plan (§3)).
A system design.
A prioritisation and distribution between group members of user-stories.
Every member of the group has to have made a commit to the main branch in the Git repository.
Give the presentation version of the repository a tag
m1, see Git (§3.1).Push to the
mainbranch of the repository, before 23:59, the day before.
17/06 Presentation of MVP M2
In this meeting you should present your MVP. The goal of this meeting is to assess what is important for the customer.
Every group will have 15 minutes to present and ask for feedback (see 2026 Course Plan (§3)). You get points for every user-story you can demonstrate work.
An working implementation of a system.
Prepare demonstrations of successful user-stories.
Give the presentation commit of the repository a tag
m2, see Git (§3.1).Push to the
mainbranch of the repository, before 23:59, the day before.
24/06 Final Presentation F1
Today you have to present the final version of your program.
Every group will have 15 minutes to present (see 2026 Course Plan (§3)). You get points for every user-story you can demonstrate work.
The presentation of the final product.
Prepare a demonstration of implemented user-stories.
Give the presentation commit of the repository a tag
f1, see Git (§3.1).Push to the
mainbranch of the repository, before 23:59, the day before.
26/06 Hand-in of Report F2
Today, you have to hand in everything.
Hand in the repository including the report.
Hand in individual reflections.
Hand in short video presentation of the final product.
Presentation Schedule §3
When you are going to present to the customer, you are presenting after the following schedule.
| Time | Group |
|---|---|
| 09:00 | Group 01 |
| 09:15 | Group 02 |
| 09:30 | Break |
| 09:45 | Group 04 |
| 10:00 | Break |
| 10:15 | Group 05 |
| 10:30 | Group 06 |
| 10:45 | Group 07 |
| 11:00 | Group 08 |
| 11:15 | Break |
| 11:30 | Group 09 |
| 11:45 | Group 10 |
| 12:00 | Group 03 |
| 12:15 | Break |
| 12:30 | Break |
| 12:45 | Break |
| 13:00 | Group 11 |
| 13:15 | Group 12 |
| 13:30 | Group 13 |
| 13:45 | Group 14 |
| 14:00 | Break |
| 14:15 | Group 15 |
| 14:30 | Group 16 |
| 14:45 | Group 17 |
Re-exam §4
The re-exam works like an extension to the project, where you will be given 3+ new user stories, that you have to implement over a 3 week period.
You can work in a group of your choosing or individually.
You can continue working on the code you handed in at the exam or a fresh version of the fordel repository.
On the 24th of July, after the reexam registration period, if you are signed up for the reexam, you will be given 3+ user stories, which you implement.
On the 13th of August, you will upload a
reexam.bundlefile with your repository to Learn.After which we will agree on an oral examination date, where you will be asked to present your solution as well as asked to implement a small extension to the project.