🏁 Sprint 9, In One Line: Build the Frontend. Cap Off the Project.
"Nine sprints of real work is behind you. Sprint 9 is where you build the thing that finally shows it — a real frontend, a real product, the thing you point to on Demo Day and say: this is what we built."
This is the clearest instruction of the term: this final sprint is about building your frontend, and using it to cap off the whole project. Everything else — the pipeline, the calibration, the automation — is the engine. This week is where you build the dashboard on top of it and make the whole thing look, and feel, like a real product.
Sprint 8 was about hardening what runs underneath. Sprint 9 is about what the room actually sees. A working pipeline nobody can see clearly is a much weaker Demo Day than the same pipeline presented through a frontend built to show it off.
Sprint 9 exists to answer one question for every team: when we open your project on Demo Day, does it look like something real — a product, not a script?
Any team can point to a pipeline that produced output this week. That is not what separates a pass from a distinction on 3 August. The question is: what's the proof this has been a real system, not a one-off?
A team opens Demo Day by running the pipeline live, it produces a prediction, and they treat that as the whole story.
One successful run proves the code works today. It does not prove the system learned anything, survived any failure, or was ever running without someone watching it. That proof lives in your commit history, your tags, and your calibration table — not in a single live execution.
By Demo Day, your team should be able to answer yes to each of these, with a screen open to prove it:
• Can you show a github-actions[bot] commit from at least one week where no human touched the pipeline?
• Can you show a moment where an API call failed or was rate-limited, and the fallback handled it — not a human patch?
• Can you show the cumulative calibration table from Week 22 through Week 31 — not just this week's number?
• Can every team member explain, in their own words, the part of the system they own?
If the answer to any of these is no, that's what this week is for — not adding something new, but making one of these answers true.
It doesn't mean a scripted performance. It means every person knows exactly which screen, which file, which commit they're pointing to when they say "here's the evidence" for their own part of the system. That clarity is what makes a presentation feel professional rather than improvised.
You've run this chain eight times already. This sprint it isn't a new risk to manage — it's the evidence itself. The chain that ran cleanly, sprint after sprint, is your case for a distinction.
Same chain as every sprint. The only thing that changes this week is what a broken link now costs you — there's no Sprint 10 to fix it in. One missing link this week shows up live, in the room, on Monday.
R2's job this week is the same as always — watch the chain from Monday, not Sunday — plus one new job: confirm every role knows exactly what they're presenting and can speak to it clearly.
"This is it — last sprint. Your pipeline is the engine — now let's build the frontend that shows it off. If something's still shaky underneath, fix that first, then put a real face on it. And everyone: say your two minutes out loud to the team at least once before Monday."
vW31Exact format: lowercase
v, capital W, two digits. This is the record that seals the project.
The full nine-sprint accuracy trend, not just this week's delta. R10 owns this — it is the single most differentiating artefact on Demo Day.
retrospective_W31.md committed, and every role knows exactly which segment they present Monday.
The mid-week check-in and dependency discipline do not relax because it's the last sprint — if anything, they matter more, because there is no next sprint to absorb a slip.
sprint_goal_W31.md committed before end of Monday.standup_midweek_W31.md committed by Wednesday 23:59 SGT, naming every role.vW31 cut, retrospective_W31.md committed, cumulative calibration table finalised before midnight.
| When | What happens | R2's responsibility |
|---|---|---|
| Mon 27 | SPRINT PLANNING Final sprint goal set: reliability and clarity, not new scope. |
Facilitate. Confirm every role knows their Demo Day segment. Commit sprint goal today. |
| Tue–Wed | EXECUTION + CHECK-IN Final reliability fixes only. Roles begin drafting their two-minute segment. |
Contact every role individually by Wednesday. Commit standup_midweek_W31.md by Wed 23:59. |
| Thu 30 | SYNTHESIS GATE Same dependency gate — R8 waits on R3, R4, R5. |
Confirm all agent outputs are committed before R8 starts. |
| Fri–Sat | AUTOMATED FETCH + FINAL SYNC Pipeline runs on schedule. Team confirms Demo Day roles and evidence links are final. |
Confirm the fetch ran without intervention. Organise the full run-through. |
| Sun 2 Aug · 23:59 | SPRINT SEALED — FINALvW31 tag cut. Cumulative calibration table finalised. Retrospective committed. |
Confirm all DoD items checked. Sign off before R9 cuts the final tag. |
| Mon 3 Aug | FINAL DEMO DAY Every role presents their two-minute segment, live, with evidence. |
Open the presentation. Introduce the team's nine-sprint story before handing to each role. |
Several teams have asked whether they can build a frontend this sprint. The answer is: please do — and don't hold back. Nine sprints of solid data and a working pipeline deserve to be seen as something real, not scrolled past in a terminal window. If you've got the system working, spend real time this week turning it into something that looks like it could ship — a live dashboard, a clean results page, your predictions and calibration history rendered so it actually looks like a product someone built to use, not a script someone ran.
This is the best way to prove everything else you built actually works, because a reviewer believes what they can see clearly far more than what they're told about. Two teams walking in with the same accuracy numbers will not read the same on Demo Day if one of them opens a polished dashboard and the other opens a JSON file.
If you have the bandwidth, this is genuinely worth the rest of this week. One real guardrail: don't let the frontend become an excuse to stop checking the backend still runs clean — a beautiful dashboard sitting on top of a broken pipeline is worse than no dashboard at all. But if your pipeline is solid, go build something you'd actually be proud to open in front of the room.
Every role presents their own two-minute segment on Demo Day. This sprint, actually running that sequence out loud as a team — at least once, before Monday — is expected and will show in how the presentation goes.
Not just this week's delta. The full nine-sprint trend is the artefact that shows whether the system actually learned — it is the hardest thing to fake and the easiest thing to verify live.
standup_midweek_W31.md committed by Wednesday 29 July 23:59 SGT is still mandatory, named per role, with any blockers and R2's response action documented.
vW31 tag before Sunday midnight. Have the Actions run history open and ready Monday.standup_midweek_W31.md committed by 23:59.Post in your team channel before Sunday 2 August 23:59 SGT.
TEAM: Team __ / Practical __ SPRINT: 9 · vW31 · FINAL GITHUB REPO: RELEASE LINK: ━━━ SM CHECK-IN (R2) ━━━ standup_midweek_W31.md committed by Wed 29 Jul: Y/N All roles clear on their Demo Day segment and evidence: Y/N Final team sync completed: Y/N · when: ━━━ SPRINT GOAL ━━━ Our Sprint 9 goal was: Did we meet it: Y / Partial / N ━━━ PREDICTION ━━━ File committed (prediction_W31.json or .md): Y/N SPX direction + confidence: NDX direction + confidence: IWM direction + confidence: All 11 sectors covered: Y/N Human Score Wild Card applied: Y/N Wild Card reasoning: ━━━ PIPELINE ━━━ Automated fetch ran Sat morning SGT with no human intervention: Y/N GitHub Actions run URL: All branches merged before final tag: Y/N ━━━ AGENTS (all committed before R8 synthesis) ━━━ Almanac R3 committed by Thu: Y/N Macro R4 committed by Thu: Y/N Technical R5 committed by Thu: Y/N ━━━ AI SYNTHESIS ━━━ LLM 1 via API: Y/N · model: LLM 2 via API (fallback): Y/N · model: Fallback demonstrated working: Y/N ━━━ CALIBRATION — CUMULATIVE ━━━ Cumulative table W22–W31 committed: Y/N Overall direction accuracy across all 9 sprints: Did accuracy improve over the term: Y/N ━━━ SCRUM HEALTH — FINAL ━━━ retrospective_W31.md committed: Y/N Every role R1–R10 clear and ready for Mon 3 Aug: Y/N One thing this team is proudest of across all 9 sprints:
Same rule as every sprint — R2 must contact each role member individually and document the result in standup_midweek_W31.md, naming each role with a status line. This is the last time it's assessed. Don't let it slip because it's the final week.
Lowercase v, capital W, two digits. This is the final release tag of the term — get the format right the first time.
If your pipeline still needs a manual step, or a piece isn't working, close that gap before you sink hours into the frontend — a beautiful dashboard on a broken pipeline is worse than no dashboard at all. But once it's solid, the frontend is exactly where the rest of this week should go.
You were never assessed on whether you predicted the market correctly. You were assessed on whether your team ran a professional delivery cycle — planned, executed, reviewed, and retrospected — with a system that improved sprint over sprint. Sprint 9 and Demo Day are where that whole story gets told at once.