Sprint 1 — vW1
First class of TR3, and a real sprint — just not a product one yet. No market-intelligence work is due, but there's a genuine goal, a real backlog, and a review at the end of it. By the end of this week your team exists, is equipped, and your GitHub access is proven to work.
The Convention — Read This First
The tag you'll see on every sprint (vW1, vW2, ... vW9) is just the sprint number. Not a calendar week number, not an ISO week — the same number, every time. If it's Sprint 4, the tag is vW4. That's the whole rule.
It's skipped in the sequence entirely — you won't see a "Sprint 5.5" or a gap tag. Sprint 5 is followed by Study Week (unnumbered), then Sprint 6 picks up where the count left off.
Demo Day is the Monday after Sprint 9 closes. It has no sprint number and no tag. Nothing new is predicted or submitted that week — it's presentation only.
The Trimester at a Glance
| Sprint | Tag | Monday | Notes |
|---|---|---|---|
| Sprint 1 | vW1 | 14 Sep | Team formation — you are here |
| Sprint 2 | vW2 | 21 Sep | Teams form, first deliverable opens |
| Sprint 3 | vW3 | 28 Sep | |
| Sprint 4 | vW4 | 5 Oct | |
| Sprint 5 | vW5 | 12 Oct | |
| Study Week — Mon 19 – Fri 23 Oct · no sprint number, no tag | |||
| Sprint 6 | vW6 | 26 Oct | |
| Sprint 7 | vW7 | 2 Nov | |
| Sprint 8 | vW8 | 9 Nov | |
| Sprint 9 | vW9 | 16 Nov | Final numbered sprint |
| 🏁 Demo Day — Monday 23 Nov · last face-to-face · not a sprint, no tag | |||
Sprint 1 Backlog
Each item has a real definition of done — not "I did it," but something that actually shows up as evidence.
- Read the Architecture Constitution — the technical rules every team's pipeline must follow, before you write a line of code.
- Set up your GitHub token — follow the PAT Checklist to scope it correctly.
- Prove the token works — definition of done: one verified commit to a repo, not just having read the checklist. A working token you haven't tested is not a done task.
- Form your team and set up Discord + Figma — announced and coordinated live during this week's practical.
Sprint Review
Before planning ahead, review what came before. This sprint's review looks back at last trimester.
What worked, what's changing, and why — covered live during the practical.
Looking Ahead
- Teams and the first market-intelligence deliverable are announced at the start of Sprint 2 (vW2, 21 Sep).