Sprint : Week of 2025‐10‐25 - CMPUT301F25quartz/quartz-events GitHub Wiki
Sprint Week of 2025-10-25 — Team Quartz
1) Sprint Overview
- Sprint #: 1
- Dates: Mon 27 → Sun 2 Nov
- Goal / Theme: Half-Way Checkpoint
- Definition of Done (DoD):
- Code reviewed
- Tests passing (unit/instrumented)
- Docs updated
- Deployed to dev
2) Committed Work (Backlog Items)
| ID | Owner(s) | Est. Timeline | Status | Notes |
|---|---|---|---|---|
| US 02.01.01 | Precious | Today | ☐ Completed | |
| US 02.01.01 | Precious | Today | ☐ Completed | |
| US 02.02.01 | Precious | Today | ☐ Completed | |
| US 03.04.01 | Dinma | Today | ☐ Completed | |
| US 03.05.01 | Dinma | Today | ☐ Completed | |
| US 03.01.01 | Dinma | Today | ☐ In Progress | |
| US 01.05.04 | Divine | Today | ☐ Completed | |
| US 01.05.05 | Divine | Today | ☐ Completed | |
| US 01.01.03 | Divine | Today | ☐ In Progress |
3) Individual Weekly Updates
Precious
- Done:
- Creating an event
- Adding in the QR generator
- In-Progress:
- Editing an event
- Blockers / Risks:
- Javadocs
- The functionality
- Help Needed / Decisions:
- Need to decide how the list of events is going to look like
Onami
-
Done:
- Created the "manage events" page with all the events made by the organizer (basic UI)
- Created the buttons needed (notify, QR code, edit, select, etc)
- Set up the notify entrants buttons to bring up options for selected, chosen, declined, or waiting list
- Set up the send notifications system
- tested functionality with dummy data
-
In-Progress:
- Figuring out how to connect with Firebase
- How the draw works to select an entrant
-
Blockers / Risks:
- Need more info on how to get the users from Firebase
-
Help Needed / Decisions:
- Decided to make dummy data first to test
- Decided to draw entrants randomly
- Set up an inbox collection in Firebase for all entrants
Divine
- Done:
- Display total entrants on the waiting list
- Display lottery criteria
- In-Progress:
- Event Details page
- Blockers / Risks:
- N/A
- Help Needed / Decisions:
- Need to settle on the design of the event details page cause the figma design is difficult to recreate
Dinma
-
Done:
- Implemented AdminEventsFragment
- Implemented AdminUsersFragment
- Created AdminActivity with Bottom Navigation
-
In-Progress:
- Implement delete functionality (US 03.01.01)
- Finish Javadoc documentation
- Add confirmation dialogs
- Capture screenshots for PR
- Complete all test cases
-
Blockers / Risks:
- Certain drawable resources not displaying correctly. Soln: Ensure to set the minimum to 48dp
-
Help Needed / Decisions:
- Precious explain switch from General Profile to Admin Profile
Temi
- Done:
- Creating an entrant class
- In-Progress:
- Creating the profile/log in page
- Blockers / Risks:
- N/A
- Help Needed / Decisions:
- How to connect the profile page to the organizer and admin pages
Kulnoor
- Done:
- Set up InboxFragment, NotificationAdapter, and NotificationModel.
- Implemented RecyclerView for displaying notifications.
- Built basic UI and tested with local mock data.
- In-Progress:
- Cleaning UI layout and button styles.
- Replacing demoUser with actual user IDs.
- Connecting fragment logic to real Firebase data.
- Blockers / Risks:
- Need consistent Firestore schema for notifications.
- Help Needed / Decisions:
- Confirm Firestore path structure (org_events → waiting_list → userId → inbox).
5) Demos / Artifacts
-
Screens / GIFs / Links:
-
QA Notes:
6) Decisions & Changes
-
Tech / Architecture:
-
Process:
11) Next Sprint Draft
- Proposed Goals:
- Have our backlog completed by Tues 4 Nov.
- Set meeting for Wed 5 Nov
- Designate tasks for completion of deliverables required for submission