Schedule
The course has the following weekly sessions:
- Wednesdays and Fridays at 11:00 - 13:45 in classroom 5003 (Pasila).
50% session attendance is required for a passing grade. Activity during the weekly sessions affects the assessment.
On the second 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.
| Date | Topics | Exercises |
|---|---|---|
| 21.10.2026 | Introduction to software development projects | Exercises 1 - 13, deadline: Before the Wed 28.10.2026 session |
| 28.10.2026 | Version control: Git and GitHub | Exercises 1 - 17, deadline: Before the Wed 4.11.2026 session |
| 4.11.2026 | 🏃♂️ Sprint 1 Planning, Scrum backlogs, GitHub Projects, Daily Scrum | Exercises 1 - 25, deadline: Before the Wed 18.11.2026 session |
| 11.11.2026 | Sprint 1 continues: Backend deployment, Sprint Review preparations | Sprint 1 exercises |
| 18.11.2026 | Sprint 1 Review & Retrospective → 🏃♂️ Sprint 2 Planning, REST APIs | Exercises 1 - 27, deadline: Before the Wed 2.12.2026 session |
| 25.11.2026 | Sprint 2 continues: Frontend and backend communication & Frontend deployment | Sprint 2 exercises |
| 2.12.2026 | Sprint 2 Review & Retrospective → 🏃♂️ Sprint 3 Planning, Testing | Exercises 1 - 20, deadline: Sun 13.12.2026 at 23:59 |
| 9.12.2026 | Sprint 3 continues: Finishing the project | Sprint 3 exercises (remember mandatory peer review and final report!) |