Sprint 2: March 11th - 18th

Work Planning

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

• Same description as the last sprint meeting.

User Story Feature Implementation

• For this weeks Sprint Work Planning, we are still prioritizing the user stories that are aimed to be complete by the Halfway-Checkpoint, in which were separated into groupings, seen in the Sprint Meeting prior to this week.
• Once the user stories marked for the halfway checkpoint were implemented, group members are encouraged to test and provide bug fixes if necessary.

Sprint Retrospective

What went well?

• Work was able to be completed in accordance to group communication, regarding which features are to be implemented one after the other.
• Occasionally shifting to collaborative work sessions (whether in person or on call) significantly improved communication and reduced the confusion that came from members working on features in isolation. Working together in real time allowed us to catch issues early, align on implementation decisions, and avoid the merge conflicts that arose from parallel independent work.

What could be improved?

• Initially, assigning features to individual members to implement separately led to confusion and frequent merge conflicts, making integration difficult. Going forward we recognized that coordinating work sessions where multiple members contribute on a single device or branch is more effective for our group. This is reflected in the reduced individual branch commit activity during periods where we were working collaboratively.

Sprint Review

Work completed

• Most of entrant and organizer features are either implemented, or planned out.

Work not completed

• Yet to work on admin features.

Current system state

• Most of entrant related features are implemented in the working build.
• Most of organizer related features are implemented in the working build.