Sprints¶
The project unfolds across 5 sprints (S0–S4). Each sprint builds on the previous one: S0 gets everyone set up and working; S1–S3 are the main development sprints; S4 closes the project with a polished release, presentation, and retrospective.
See the Schedule for sprint dates and the Syllabus for an overview of the grading structure.
| Sprint | Dates | Weight | Status |
|---|---|---|---|
| S0 — Project Onboarding | Sep 1–17 | 100 pts (9%) | Closed |
| S1 — Project Development & Release | Sep 22–Oct 8 | 100 pts (10%) | Active |
| S2 — Core Development | Oct 13–29 | TBD | Coming soon |
| S3 — Hardening & Integration | Nov 3–19 | TBD | Coming soon |
| S4 — Release & Retrospective | Nov 24–Dec 10 | TBD | Coming soon |
What every sprint looks like¶
Each sprint follows the same basic rhythm:
- Plan — pull issues from the backlog, assign owners, scope the work.
- Build — implement features through the full PR workflow (branch → code → test → review → merge).
- Log — capture all AI interactions as you go (see AI Log Instructions).
- Report — write a sprint report summarizing what was done, what was learned, and what comes next.
- Release — tag a release marking the sprint's end state.
- Reflect — complete the individual reflection survey.
- Present — deliver a lightning talk or showcase presentation (schedule varies by sprint).
Detailed requirements for each sprint are on the sprint's own page (links in the table above).