Project Process & Evidence¶
This section is the assessment/evidence entry point. Product and developer documentation explain how
the system works; this section shows how the team planned, reviewed, tested and documented the work.
Authoritative evidence remains under evidence/ and is linked rather than copied into MkDocs.
Start by evidence type¶
| Need | Start here |
|---|---|
| Sprint planning, stand-ups, stakeholder records and close-outs | Sprint Evidence |
| Original Teams meeting transcripts and readable PDF copies | Team Meeting Transcripts |
| Requirements/rubric traceability | Sprint 1 traceability / Sprint 2 traceability |
| Testing, validation and formal user-testing evidence | Testing & Validation Evidence |
| Architecture and project decisions | Decisions Index |
| AI registers and AI transcript evidence | AI Use & Evidence |
| Project workflow and ceremonies | Project Methodology |
| Backlog and milestone planning | Project Backlog & Milestone Plan |
Methodology¶
The project uses the Project Methodology for Sprint planning, workflow, reviews and retrospectives. Source-control practice is documented separately in the Git Methodology. The Sprint Evidence page is the chronological route from those methods to retained records.
Testing and validation¶
Use Testing & Quality for the testing method. Use Testing & Validation Evidence for the retained evidence and traceability produced by that method.
Decisions¶
Decisions Index is the single navigation point for Architecture Decision Records and other project-level decisions. Architecture pages link back to the relevant records instead of repeating the decision history.
AI use and compliance¶
AI Use explains the repository process. AI Use & Evidence links the per-member registers and AI interaction transcripts. These AI interaction transcripts are separate from the Microsoft Teams meeting transcripts indexed under Team Meeting Transcripts.
Repository evidence root¶
The repository-level evidence README explains the evidence directories and integrity rules. Normal product documentation should not be used as a substitute for retained evidence, and retained evidence should not be duplicated into the public docs merely to make it visible.
AI Declaration¶
The process/evidence information architecture and evidence-type routing were reorganised with the assistance of ChatGPT-Web[GPT-5.6 Sol].