Schedule
The course has weekly sessions on in classroom 4012 on Tuesdays at 12:00 - 13:45 and on Fridays at 9-10:45 (excluding Fri 29.3. which is an Easter holiday and Tue 30.4. which is May Day Eve). Attendance on weekly sessions is mandatory.
On the third week the teams start working on the project. The project advances in two week iterations called sprints. There are requirements for each sprint. During the sprint teams work with the Sprint requirements with the guidance of the teacher during the weekly sessions and independently outside the sessions.
| Week | Topics | Exercises |
|---|---|---|
| 25.3. | Introduction to software development projects | Exercises 1 - 14, deadline on 2.4. at 12:00 |
| 1.4. | Version control: Git and GitHub | Exercises 1 - 17, deadline on 8.4. at 12:00 |
| 8.4. | 🏃♂️ Sprint 1: Sprint Planning, Scrum backlogs, GitHub’s workflow | Exercises 1 - 32, deadline on 22.4. at 12:00 |
| 15.4. | Daily Scrum, Git branches, Sprint Review | |
| 22.4. | 🏃♂️ Sprint 2: Retrospective, REST APIs | Exercises 1 - 35, deadline on 6.5. at 12:00 |
| 29.4. | Communication between frontend and backend | |
| 6.5. | 🏃♂️ Sprint 3: Testing | Exercises 1 - 27, deadline on 20.5. at 11:00 |
| 13.5. | Finishing the project |