end sprint1 status - Andre-asn/Quack-Campus-Event-Coordinator GitHub Wiki
Project: Quack! Campus Event Coordinator
Sprint: Sprint 1
Reporting period: September 29 - October 14, 2026
Overall Status
🟢 GREEN
Sprint 1 is complete. All three features and all nine stories are closed, with no work carrying over into Sprint 2. Repository setup, the full CI/CD pipeline, and Stevens Google sign-in are merged to main, so every merge now builds, tests, and deploys the API. No team-reported blockers have been recorded.
| Sprint 1 measure | Count |
|---|---|
| Features complete | 3 of 3 |
| Stories closed | 9 of 9 |
| Stories carried over | 0 |
| Team-reported blockers | 0 |
Feature Status
Design status reflects the Technical Design Doc covering the data model, API, and wireframes. Completion below reflects merged work and verified repository status.
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 | Complete | Complete | Yes |
| Stevens Google sign-in (#10) | Yes | Complete | Complete | Complete | Yes |
- Repository and build setup: the API runs locally with one command (#18), and the client runs from a fresh clone (#27). README setup instructions are available.
- Continuous integration and deployment: pull requests run build and test checks automatically (#20), integration tests run against PostGIS (#21), merging to main deploys the API to Railway (#22), and new issues are added to the project board automatically (#23).
- Stevens Google sign-in: PR #33 delivered Google sign-in (#24), server-side Stevens domain restriction (#25), and session persistence (#26).
Resource Utilization
| Team member | Prior week | Upcoming week |
|---|---|---|
| Andre Santiago-Neyra | Implemented automatic Railway deployment, including the API Dockerfile and deployment workflow, and merged it through PR #32, closing #22 and the CI/CD feature (#9). Reviewed PR #33. | Kick off Sprint 2 and begin assigned stories for event creation and map discovery. |
| Pratiksha Vilas Pawar | Completed PostGIS integration testing (#21). Corrected Java source/test placement, updated README instructions, and merged PR #31 after successful API and client CI checks. Reviewed PR #32. | Begin assigned Sprint 2 stories and prepare test coverage for event creation and map queries. |
| Zhong Zhangniantong | Delivered Stevens Google sign-in through PR #33, covering sign-in, domain restriction, and persistent sessions (#24 to #26), closing the sign-in feature (#10). | Begin assigned Sprint 2 stories for event creation and map discovery. |
Team Activities
Sprint 1 review and follow-up
- Purpose: assess completed foundation work and close out the remaining Sprint 1 items.
- Contributors: Andre Santiago-Neyra, Pratiksha Vilas Pawar, Zhong Zhangniantong.
- Outcomes:
- PostGIS integration testing was merged through PR #31, passing both API build/tests and client type checking.
- Deployment review feedback on PR #32 was addressed and the PR was merged, completing the CI/CD feature.
- Stevens Google sign-in was reviewed and merged through PR #33, completing the final Sprint 1 feature.
- Follow-up: resolve the branching strategy before Sprint 2 product features are integrated.
Changes and Major Decisions
| Area | Change | Reason | Impact |
|---|---|---|---|
| Testing | PostGIS integration tests and the extension migration were merged through PR #31. | Verify spatial queries against a real database and make test execution repeatable. | Story #21 is closed; future event queries build on this test foundation. |
| Deployment | The API is hosted on Railway alongside the database, deployed automatically on merge to main (PR #32). | Consolidate API and database hosting on one platform. | Story #22 is closed; every merge to main now reaches the deployed environment. |
| Sprint scope | Working Mapbox integration remains assigned to Sprint 2. | Keep Sprint 1 focused on setup, testing, deployment, and authentication. | The working map was not required for Sprint 1 completion. |
No additional scope changes are proposed. Sprint 2 begins with no carryover. The branching strategy remains under discussion.