Deadlines
Weekly Stand-ups¶
Every week starts with a stand-up — 4 minutes per team. No slides, no show: just clear answers to three questions:
- What did we finish?
- What are we doing next?
- What is blocking us?
If you don’t show it, it doesn’t exist. Feedback only comes on visible work. Timebox is strict, so prepare together.
Bus Factor – Lottery Factor
How many people could disappear before the project collapses? If the answer is “one,” your bus factor is dangerously low. Knowledge must be shared, code and docs published, so the project can survive sickness, vacations, or even someone “winning the lottery.” A team is only safe when no single absence can sink it.
Payroll Rules¶
Think of points like payroll: deductions for missing progress, bonuses for great contributions.
Attendance is not enough
Coming unprepared or without progress more than once can cost your team up to 30 points, based on your boss (tutor)'s expert judgement.
Bonus points
Extra effort or strong in-class contributions can earn up to 30 bonus points, based on your boss (tutor)'s expert judgement.
Milestone Demos¶
Three milestone demos, 5 minutes per team. Treat them like board meetings: short, focused, results only.
Deadlines are real
Deliverables are due 3 business days before the demo at 08:00. Example: demo Friday → deadline Tuesday 08:00. Demo Monday → deadline Wednesday 08:00 (previous week).
| Milestone | Demo Week |
|---|---|
| Team building | Week 4 |
| Planning | Week 7 |
| Development | Week 13 / Final week of the teaching period |
| Quality Assurance | Week 13 / Final week of the teaching period |
Single source of truth
The repository is the official record of your project. Everything must live there: issues, README, and wiki pages. If it’s not in the repo, it doesn’t count. Slides, personal notes, or chat messages are useful for coordination, but they are not deliverables. Think of the repo as your team’s shared office: it’s where the work is stored, tracked, and verified. This habit is essential in real projects — without a single source of truth, knowledge gets lost, progress can’t be seen, and the team falls apart.
Extensions & Late Work¶
Deadlines are contracts in real jobs. Here you get some safety net, but only once per milestone. Think of it as practice: small flexibility here, no flexibility later.
Extensions
You can ask for a one-week extension once per milestone, but only in person during class. This option is not available for the final milestone.
The deadlines for the following milestones will not change.
Even if you get an extension, you still have to submit your work at least 3 business days before the presentation.
If you request an extension, you may continue working on the assignment during the last 3 business days before the original presentation date.
Example:
Presentation of Milestone X: February 13, 2026, 10:00 AM
In this case, the submission deadline was February 10, 2026, 8:00 AM.
You ask for the extension in person during class on February 13, 2026. You don’t need to stop working while waiting for the extension to be confirmed — you can keep working between February 10 and February 13, 2026.
New submission deadline after the extension: February 17, 2026, 8:00 AM
New presentation date after the extension: February 20, 2026, 10:00 AM