Skip to main content

Sprint 1

(2026-08-02 → 2026-08-25)

(Taken directly from our Gitea Milestone for Sprint 1, used as the sprint's defined goal and scope.)

Goal​

Get the project's foundational infrastructure in place — authentication, database connectivity (local and Azure), CI/CD, testing setup, and initial documentation content — so feature development in Sprint 2 isn't blocked on missing scaffolding. This milestone also covers the Initial Design & Dev Plan required for Milestone 1, scored separately from setup implementation.

Scope — Implementation​

  • Working authentication (sign up, sign in, password reset, etc.)
  • A documented local database setup so every teammate can run a matching local database
  • Proven frontend ↔ backend ↔ database connectivity end to end
  • Azure infrastructure provisioned and reachable
  • Automated deployment to Azure on merge to main
  • Automated test runs on every PR
  • A working test pattern (Jest) for both frontend and backend
  • Architecture and Database Schema pages on the documentation site

Initial Design & Dev Plan is also part of this milestone's scope but is scored separately — see the Initial Design and Dev Plan page for that content.

Ceremonies Held​

Being transparent about where we actually are, rather than overstating our process:

  • Sprint Planning: done — captured as the Gitea Milestone goal/scope above, with issues created and assigned against it.
  • Daily Standups: While daily standups are not currently conducted as a formal, documented ceremony, the team holds daily check-ins and discussions through WhatsApp to communicate progress, upcoming tasks, and any blockers.
  • Sprint Review: conducted with our client tutor on 25 Aug 2026 — Sprint 1 deliverables were demoed (authentication flow, CI/CD pipeline, Azure deployment), and MS1 documentation task ownership was assigned across the group. See the full Stakeholder Interaction Log for dated meeting notes, decisions, and follow-through evidence. This is distinct from the marking tutor, who evaluates the team but is not the stakeholder the Sprint Review is held with.
  • Sprint Retrospective: not yet formally run for Sprint 1. Planned to be introduced from Sprint 2 onward.

These ceremonies are being formalized going into Sprint 2, where the "Actively following methodology" criterion carries the same 10% weight and explicitly expects ongoing evidence.

Evidence​

  • Gitea Milestone for Sprint 1, with a written goal and scope
  • Gitea Issues / Projects board showing task breakdown and status
  • PR and commit history showing incremental, reviewed delivery
  • Sprint review — held with client tutor this sprint (see above)
  • Sprint retrospective notes — to be introduced from Sprint 2 (Scrum Master to own)
  • Daily standup log — to be introduced from Sprint 2, if adopted (Scrum Master to own)