Project deadlines
- 14 September: team formation - project selection - customer contact
- 28 September: 1st iteration (two weeks)
- 19 October: 2nd iteration (three weeks)
- 16 November: 3rd iteration (four weeks)
- 14 December: 4th iteration (four weeks)
Note: You do not have to submit any files or documents through Moodle. Your grade for each iteration is determined by the state of all your project artifacts-deliverables on your chosen collaboration platform (e.g., GitLab or the Atlassian suite) at the time of each iteration's deadline. More specifically:
- For all assets tracked in Git—such as your source code, automated tests, and CI/CD configuration—you must formally mark your submission by creating an annotated Git tag. This tag points to the exact commit that we will pull and grade.
- For all other project artifacts—such as your issue tracker and wiki pages—we will evaluate their content and status as they exist precisely at the deadline.
- It is your responsibility to ensure all required deliverables are complete and correctly reflected across your tools. The deliverables and the evaluation criteria for each iteration can be found on the course website and will also be provided in the corresponding iteration evaluation sheet by the start of each iteration.
Other deadlines
- 22 October: Intermediate demo day
- 12 November: Will send you a message with information about peer review
- 19 November: Deadline for selecting a project to peer-review
- 29 November: Peer reviews due
- 14 December: Peer review responses due
- 18 December: Final Demo Day
All deadlines are set to 24:00 (EEST). If you want a deadline extension, you need to explicitly ask it from your mentor. The mentor will apply the following penalties:
- 24 hours deadline extension: the team's score is reduced by 20%
- 24-48 hours deadline extension: the team's score is reduced by 40%
- > 48 hours late: 100% of the points deducted.
- You can still continue participating and get a positive grade, but the points for this milestone are lost.