Sprint 1: March 4th ‐ 11th - CMPUT301W26glitch0/glitch0-events GitHub Wiki

Sprint 1: March 4th - 11th

Work Planning

Halfway-Checkpoint Deliverables (Due March 13th, 2026)

The following are descriptions on the deliverables for the halfway checkpoint. Portions of the halfway checkpoint deliverables are being approached in the same way that the work in Project Part 2 was divided, where all members are updating their previous work in accordance to TA feedback.

  • Product Backlog : Ege & Varad

    • Added user stories to the project board by creating each user story as an issue, available for all members.
    • Provided acceptance criteria to each issue, along with labels corresponding to Risk Level, Story Points, and Halfway Checkpoint.

  • User Interface Mockups and Storyboard Sequences : Leo & Justin

    • TODO: Correct the transition lines so that they match the element of the screen that triggers them.
    • TODO: Fix colouring for buttons, as mix use of red and blue may lead to confusion.
    • TODO: Include QR invalidity within the story board.
    • TODO: Fix certain text rendering/overlapping
    • TODO: Remove "Not needed?" caption under screen 6 in the Admin Mockups

  • CRC Cards : Hanson & Taehun

    • TODO: Add changes/fixes to CRC Cards in reference to TA feedback.

  • Code Base of Prototype, Code Documentation, Test Cases

    • As it currently stands, these deliverables are split in accordance to the feature that each member implements. Put simply, Code base is split into parts, members working on said parts deliver code documentation and test cases for their implemented code.

  • Object Oriented Design

    • Created model classes are tracked and kept note of during work. Done to ensure understanding of class relationships and navigability, allowing for UML diagram creation when needed.

User Story Feature Implementation

The following user stories are features aimed to be complete by the Halfway-Checkpoint, divided by implementation dependency. Divided user stories are assigned to members with possibility for collaboration, and are subject to change if needed.

  • Device Identity & Profile : Leo

    • US 01.07.01 - Device identification, no username/password
    • US 01.02.01 - Profile creation with name, email, phone
    • US 01.02.02 - Profile editing

  • Event Creation & Organizer Setup : Leo

    • US 02.01.01 - Create event and generate QR code
    • US 02.01.04 - Set registration period
    • US 02.03.01 - Optional waiting list limit

  • Event Browsing & Waiting List : Ege

    • US 01.01.03 - Browse list of events
    • US 01.01.04 - Filter events
    • US 01.01.01 - Join waiting list
    • US 01.01.02 - Leave waiting list
    • US 02.02.01 - Organizer views waiting list

  • QR Code Scanning & Event Details : Varad

    • US 01.06.01 - Scan QR code to view event details
    • US 01.06.02 - Sign up for event from event details page

  • Lottery Draw & Invitation Flow : Hanson & Taehun

    • US 02.05.02 - Organizer sets sample size and runs lottery
    • US 02.05.01 - Send notification to chosen entrants
    • US 01.05.02 - Entrant accepts invitation
    • US 01.05.03 - Entrant declines invitation
    • US 01.05.01 - Re-draw when entrant declines
    • US 02.05.03 - Organizer draws replacement applicant

  • Notifications & Entrant Lists : Justin

    • US 01.04.01 - Notification when chosen
    • US 01.04.02 - Notification when not chosen
    • US 01.04.03 - Opt out of notifications
    • US 02.06.01 - Organizer views invited entrants list
    • US 02.06.03 - Organizer views final enrolled list

Sprint Retrospective

What went well?

  • Members were able to communicate work processes effectively, allowing for seamless teamwork.

What could be improved?

  • Division of work between group members could be done a bit earlier next time, to allow for a bit more time when actually working on the application itself.

Sprint Review

Work completed

  • 20/24 of the Halfway-Checkpoint user stories have been marked as complete within the repo's issues.
  • UML for this versions code is completed.
  • Storyboard edits were updated to existing storyboard

Work not completed

  • As it currently stands within the repos issues tab, US 01.04.01, US 01.04.02, US 02.05.01, US 02.05.02 are the user stories that are not marked as complete.

Current system state

  • Our current application has the following general features:
    • Allows for users (entrants and organizers) to sign up with their personal information, along with updating it.
    • Organizers can create events with specifics (event type, event date, registration window, entrant registration limit, etc.)
    • Organizers can see a list of entrant users who sign up for their events.
    • Entrants can join/leave event waiting lists.
    • Entrants can filter events based on desired specifics, along with checking their event history in the My Event tab.
    • Entrants can accept/decline event invitations after lottery selection.
    • QR code is provided when events are created, allowing for entrant users to scan QR codes in which pop up the event tied to the QR code.