Sprint Evidence¶
This page is the chronological index for Sprint planning, stand-ups, stakeholder interaction,
close-out and related milestone evidence. It links to the authoritative records under
evidence/sprints/
rather than reproducing them.
Original Microsoft Teams meeting transcript Word documents and their browser-friendly PDF copies are indexed separately on Team Meeting Transcripts.
Sprint 1¶
| Date | Record |
|---|---|
| 4 Aug 2026 | Stakeholder meeting |
| 6 Aug 2026 | Sprint planning |
| 6 Aug 2026 | Stand-up |
| 11 Aug 2026 | Stakeholder meeting |
| 13 Aug 2026 | Stand-up |
| 18 Aug 2026 | Stakeholder meeting |
| 20 Aug 2026 | Stand-up |
| 25 Aug 2026 | Sprint 1 close-out and retrospective |
Repository index: Sprint 1 README.
Related: Sprint 1 requirements traceability.
Sprint 2¶
| Date | Record |
|---|---|
| 25 Aug 2026 | Sprint planning |
| 26 Aug 2026 | Stakeholder approval and WhatsApp evidence |
| 27 Aug 2026 | Stand-up |
| 1 Sep 2026 | Stakeholder meeting |
| 3 Sep 2026 | Stand-up |
| 8 Sep 2026 | Asynchronous stakeholder review and redacted WhatsApp transcript |
| 10 Sep 2026 | Weekly stand-up |
| 15 Sep 2026 | Sprint 2 close-out and retrospective |
| 15 Sep 2026 | Final stakeholder review |
Repository index: Sprint 2 README.
Related: Sprint 2 requirements & rubric traceability, User Testing Overview, and Testing & Validation Evidence.
Sprint 3¶
| Date | Record |
|---|---|
| 15 Sep 2026 | Sprint planning |
| 17 Sep 2026 | Stand-up |
| 22–24 Sep 2026 | Asynchronous stakeholder exchange |
| 24 Sep 2026 | Stand-up image |
| Sprint 3 | Production-scale deployment acceptance |
| Sprint 3 | Performance re-validation |
Repository index: Sprint 3 README.
Gitea remains authoritative for current issue state, assignees, dependencies and completion status. Sprint 3 requirements/rubric close-out should be linked here when its authoritative record exists rather than reconstructed on this page.
Additional Sprint 3 records:
- 22–24 September asynchronous stakeholder review summary
- 28 September Sprint 3 pre-finalisation close-out
Related: Sprint 3 requirements & rubric traceability.
The 28 September close-out is intentionally pre-finalisation. It must be reconciled against current main, reviewed by another team member and updated with the final milestone tag before #613 closes.
Sprint 4¶
Sprint 4 is the final project-submission milestone.
| Date | Record |
|---|---|
| 30 Sep 2026 | Sprint 4 planning and final-submission scope |
Repository index:
evidence/sprints/sprint-4/README.md
The planning record captures the refined final-submission backlog, early completed Sprint 4 work, sequencing, scope decisions, known risks and the relationship between the original roadmap and the current Gitea milestone.
Current issue status and formal dependencies remain authoritative in Gitea.
The Issue #799 Sprint 4 planning navigation update was planned, generated and edited with the assistance of ChatGPT-Web[GPT-5.6 Sol].
How to add future Sprint evidence¶
Create a new evidence/sprints/sprint-<n>/ directory, retain concise Markdown records for normal
planning/stand-up/stakeholder navigation, and add dated entries here. If a Microsoft Teams transcript
is retained as a Word document, keep the original .docx; a same-name .pdf may be added beside it
as a readable presentation copy and indexed on Team Meeting Transcripts.
Do not convert unrelated evidence formats merely for consistency.
AI Declaration¶
This Sprint evidence index was originally created with AI assistance recorded in the repository. The current information-architecture cleanup, broken Sprint 2 close-out link correction, Sprint 3 index refresh and transcript routing were reviewed and edited with the assistance of ChatGPT-Web[GPT-5.6 Sol].
The Issue #613 Sprint 3 close-out navigation update was reviewed and edited with the assistance of ChatGPT-Web[GPT-5.6 Sol].