mid sprint1 status - Andre-asn/Quack-Campus-Event-Coordinator GitHub Wiki

Project Status Report: October 6, 2026

Prepared by: Andre Santiago-Neyra, Project Lead

Overall Status

🟢 GREEN

The project is progressing as planned with no known blockers. Sprint 1 covers the foundation the product features depend on: a runnable repository, the CI/CD pipeline, and Stevens Google sign-in. Repository and build setup is complete. PR build and test checks and automatic API deployment are complete; PostGIS integration tests are pending, and Stevens Google sign-in is in active development.

Sprint 1 measure Count
Features complete 1 of 3
Stories closed 5 of 9
Stories in progress / pending 4
Blockers 0

Feature Status

Design status reflects the Technical Design Doc, which covers the data model, API, and wireframes for every in-scope feature.

Sprint 1 features

Feature Started Design Development Testing Integrated
Repository and build setup (#8) Yes Complete Complete Complete Yes
Continuous integration and deployment (#9) Yes Complete In progress In progress Partially
Stevens Google sign-in (#10) Yes Complete In progress Not started No
  • Repository and build setup: both stories are closed and merged. The API runs locally with one command (#18) and the client runs from a fresh clone (#27).
  • Continuous integration and deployment: pull requests run build and tests (#20) and merging to main deploys the API (#22) are complete. Integration tests against PostGIS via Testcontainers (#21) is in progress.
  • Stevens Google sign-in: three stories open. Sign in with a Stevens Google account (#24), reject accounts outside stevens.edu (#25), and persist the session between app launches (#26).

Resource Utilization

Team member Prior week Upcoming week
Andre Santiago-Neyra Completed the Repository and build setup feature (#8): API runs locally with one command (#18), client runs from a clone (#27). Completed automatic API deployment on merge to main (#22). Upgraded the backend to Java 25 and Spring Boot 4.0. Support completion of the PostGIS integration tests (#21). Bring the branching proposal to the team for a decision.
Pratiksha Vilas Pawar Completed the PR build and test workflow (#20). PostGIS integration tests via Testcontainers (#21) are pending. Complete #21 and verify that integration tests run locally and in CI.
Zhong Zhangniantong Began the Stevens Google sign-in feature (#10): Google sign-in (#24), stevens.edu domain restriction (#25), and session persistence (#26). All in progress. Closed project board automation (#23). Complete #24, #25, and #26 so sign-in works end to end.

Team Activities

Sprint 1 team sync

  • Purpose: review the action items each member assigned themselves for Sprint 1 and agree on how to approach them.
  • Participants: Andre Santiago-Neyra, Pratiksha Vilas Pawar, Zhong Zhangniantong
  • Outcomes:
    • Each member walked through their assigned issues in detail and confirmed their approach. No blockers were raised.
    • The team discussed how feature work will be merged to main once product features begin. One idea raised was a staging branch that is deployed continuously and then promoted to main.
  • Follow-up: decide on the branching and merge strategy before the first product feature is merged. No decision has been made yet.

Changes and Major Decisions

Area Change Reason Impact
Technology Backend moved from Java 21 and Spring Boot 3.0 to Java 25 and Spring Boot 4.0. Start on the current Java LTS release and the current Spring Boot major version while the repository is still scaffolding, instead of upgrading mid-semester. No effect on scope or schedule, since the change landed before any feature code. The CI and deployment configuration target Java 25, and the technology stack in the Technical Design Doc will be updated to match.
Sprint scope Working Mapbox screen moved from Sprint 1 to Sprint 2. Focus Sprint 1 on application setup and authentication. Successful login initially opens a confirmation screen; map integration follows in Sprint 2.

There were no changes to scope, requirements, or schedule this period. The branching strategy described under Team Activities is still under discussion and will be reported once decided.