Documentation (Sprint 1), Fall 2026

Project overview

Start here to understand the core mission, problem domain, target audience, and key goals of the product.

See Project Overview.

User stories

Read this for feature requirements, acceptance criteria, and specific user needs driving Sprint 1 development.

See User Stories and User Story Summaries.

High-level software design

Consult this to review system architecture, data models, tech stack choices, and component interactions.

See Software Design.

Low-fidelity user interface

View this visual mock-up to see the intended screen layouts and the navigation between the screens before you start design or frontend tasks.

See Wireframes. A static image is also available: Wireframe image.

Sprint planning

Check this to track task allocations, sprint backlogs, timeline milestones, and current progress metrics.

See Project Management.

Teamwork

Refer here to see the team canvas, the Scrum roles for each sprint, and the Belbin team roles.

See Teamwork.

Meeting minutes

Read the notes from the team meetings and the client meetings.

See Meeting Minutes.

Use of AI

The team members plan, direct, review, and own the work on this site. We use AI tools to check our work, to draft text and diagram changes, to make repetitive changes, and to do routine tasks, so that we save time. We do not use AI to complete a task without review. A team member reads and checks each AI change before it is committed, and each pull request needs the approval of two team members.

Entity	Resource	Subject	Date
Anthropic	Claude (Claude Code), model Claude Opus 5.5	Checking documents against the course rubric and the user stories, formatting and consistency fixes, diagram edits, and GitHub issue creation for Sprint 1 and Sprint 2	September 2026

Team members add a row for each other AI tool that they use.