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. Teams are already pre-assigned — by the end of this week your team is set up on Discord and FigJam, ready to go.
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.
Week 10 (Mon 23 – Fri 29 Nov) is the full Demo Day week — no new prediction cycle, no sprint number, no tag. Two checkpoints built in: a mandatory PR-cleanup by Wednesday (everything merged before presentation prep starts), and a live pipeline check where every team demonstrates real output in front of the class, not just a dashboard that looks right.
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 Week 10 — Mon 23 – Fri 29 Nov · PR cleanup by Wed, live pipeline check, presentations · not a sprint, no tag | |||
Sprint 1 Backlog
One thing every team needs to actually finish this week.
- Set up your pre-assigned team on Discord + FigJam — teams are already assigned, announced live during this week's practical. That's the whole deliverable for Sprint 1.
- Add your Discord username to the Team Roster Sheet — find your name, check your Discord Status and GitHub Status columns, fix anything marked MISSING or INVALID.
- Join the class Discord: discord.gg/JeEuB9kHf — you'll land in #general. Team channels open up once everyone's sorted.
See GitHub for how your team's repo is set up.
Looking Ahead
- Why This, Why Now → — wondering why an IT course involves the stock market? Start here.
- The moment your team forms today, your work begins — see Sprint 2: What Must You Do for the concrete tasks due by next Monday.