Deliverables and calendar

Milestone 1 (10%): your project and its problem statement (graded out of 5)

From Friday 20 November 2026; extra credit if handed in before Tuesday 15 December, discussed in class on the afternoon of 15 December; final deadline Wednesday 16 December 2026 at 23:59 (last commit pushed) · Deck h1

• docs/cahier-des-charges.md in the team's shared GitHub repository, last commit pushed before the deadline
• An e-mail to the teacher presenting the project and the team members
• The question in one sentence, on the model of the UCI example of session 1, with its four markers: a decision, a measure, a scope, an owner (graded)
• Lines 1 to 5 of the scope-document template: the decision, the target, the metric, the safeguards, the data (graded: one point per element complete and specific to the project, capped at 5)
• Line 6, the plan: naive, best, heavy; the milestones; who does what (mandatory, not graded)
• Who we are, in two parts: the persona (the company the team embodies, its client or counterpart, who signs), then the real people, with for each member their background, the job they aim for, why this track, their interests (mandatory, not graded: without the plan and this part, the milestone is not accepted)

Milestone 2 (25%): an OLS or a simple classification on your project

Last commit pushed before Friday 29 January 2027 (jalon-2 tag recommended) · Deck h2

• Seeded frozen split, without leakage, on your project's data
• A naive reference model
• A linear regression (OLS) or a simple classification (logistic regression)
• The chosen and justified metric, the results on validation, the test set closed
• The limits, written down
• make reproduce runs on a clean machine
• Check-in by e-mail whenever you like: reply within two working days

Final project (50%, with the presentation): your subject, with the same method

Last commit pushed the day before the final presentation (Thursday 11 and Friday 12 February 2027 block, exact day to be confirmed); final tag recommended · Deck h3

• Team formed on 14 October, core idea settled on the evening of 15 October, precise subject (and its voted category) sent by e-mail before the session of 15 December, the sooner the better
• Scope document approved in December, by pull request, then kept up to date the same way
• Public repository, same template as the thread: README, docs/, data/README.md, src/, batch/, app/, tests/, requirements.txt, LICENSE
• Three models naive, better, heavy, compared on never-seen data, the gap explained
• One command that rebuilds everything (make reproduce) and a green CI on the last commit
• FastAPI API (health, predict, version) and minimal web interface, link in the README
• Report (sections 1 to 10), one-page client memo in euros, model card, AI Act gap analysis
• Defence slides as PDF in slides/ (ten slides at most)
• One-page individual sheet per member, AI appendix; bonus outside the scheme: 300-word reflection
• Another team cloned the repository and followed the README without you
• Last commit pushed before the deadline; final git tag recommended

Final presentation with the code (50%)

Thursday 11 and Friday 12 February 2027 block (exact day to be confirmed), 08:30 to 17:30; every team attends · Deck d9

• Live demonstration ready: I clone, I run make reproduce and the API, you predict
• Each member can answer alone on the code, the method and the figures (grade adjusted orally)
• Peer evaluation sheet filled in during the other defences

The course calendar

An iCalendar file with the sessions, the milestones, the check-ins by e-mail and the defence, in Paris time. It imports into Google Calendar, Apple Calendar or Outlook.