Sprint 6 Day 1. Pipeline Audit. Sprint planning. Every team opens their GitHub repo live and walks the class through exactly what their system looks like right now — what runs automatically, what doesn't, and what the plan is for Sprint 6.
A written Sprint 6 goal from every team, read aloud before the session ends. Every Scrum Master leaves the room having committed publicly to what their team will deliver by Sunday 12 July.
Not a prediction review. Not a Sprint 5 presentation. No slides required. No submission was due this weekend — the study week contract holds. Today is about what exists in your repo right now, not what you wish you had built.
| Time | Activity | Who |
|---|---|---|
| 0:00 – 0:15 | Sprint 6 Opening — Prof Dr Tan What Sprint 6 is. What the bar looks like. Why automation is no longer optional. vW28 deadline and what full marks requires. | Prof Dr Tan |
| 0:15 – 1:05 | Team Walkthroughs — 10 minutes each × 5 teams Open GitHub live. No slides. Show the repo exactly as it is. See the format below. | All teams |
| 1:05 – 1:20 | Class Discussion What separated the automated teams from the manual ones? What would you do differently? Prof Dr Tan facilitates — honest, not harsh. | Full class |
| 1:20 – 1:45 | Sprint 6 Planning — In Teams Sprint goal. Role assignments. Definition of Done. Written live in the room. DECISION.md started. | Teams only |
| 1:45 – 2:00 | Sprint Goals Read Aloud Each Scrum Master (R2) stands and reads the team's Sprint 6 goal. One sentence. Specific. Measurable. Public commitment. | R2 from each team |
Open your GitHub repo in a browser. No slides. No prepared deck. What you show is what exists. The class sees the real thing.
Every team should be ready to answer: "Show me the last time your pipeline ran automatically." If the answer is never, that is the Sprint 6 priority. If the answer is during the study break, show the commit.
During 1:20–1:45, each team writes their Sprint 6 plan in the repo. R1 leads. R2 facilitates. Everyone contributes. By 1:45 you must have:
1. Sprint 6 goal — one sentence, specific and measurable.
2. Role assignments confirmed — who is R1 through R10 for Sprint 6.
3. Definition of Done — what does "done" mean for vW28? Written, not assumed.
4. DECISION.md updated — what is the one automation gap your team is closing this sprint?
The sprint goal format:
Example: "Deliver a fully automated end-to-end pipeline that fetches Friday closes, runs all three agent reports, calls two LLMs via API with identical prompts, and commits prediction_W28.json — all without manual intervention — sealed with vW28 by Sunday 12 July 23:59 SGT."
Sprint 6 raises every requirement. The study break was not a pause — it was time for your pipeline to prove itself. Here is what vW28 requires:
| Requirement | Sprint 5 (vW25) | Sprint 6 (vW28) |
|---|---|---|
| Prediction coverage | SPX + NDX + IWM + 5 sectors | SPX + NDX + IWM + all 11 S&P sectors |
| Release tag | vW25 |
vW28 — correct format, no exceptions enforced |
| LLM synthesis | 3 LLMs compared manually | At least 2 LLMs called via API — responses logged and compared automatically |
| Automation | At least 2 agents automated | Full pipeline runs without manual intervention no exceptions |
| Calibration | delta_W24.md | delta_W25.md + accuracy tracked across W3–W7 cumulative |
| Tag format | vW25 (some teams wrong) | Exact format vW28 — lowercase v, capital W, two digits. Wrong format = no credit. |
| Presentation | Show prediction + pipeline | Demo the pipeline running live OR show GitHub Actions log proving it ran automatically |
| Deadline | Sun 21 Jun 23:59 SGT | Sun 12 Jul 23:59 SGT — tag must be cut before midnight |