Sprint 2 Documentation
Goals of the Sprint
- Implement UI and API testing with reliable, non-flakey tests.
- Enable use of external APIs and make the project’s API available for external usage.
- Conduct extensive user testing with a formal feedback collection process and integrate results into development.
- Finalize full database schema, deployment details, and justification of design choices.
- Provide comprehensive documentation on testing, user feedback processes, and automated testing usage.
- Deliver key user-facing features: past league games, user profile (button and page), match viewer, and login page.
- Set up API with clear usage documentation.
- Improve tooling by establishing Jest, ESLint, and code coverage (target: 25% with Codecov).
Meeting Summary
| Meeting | Date | Attendees | Summary / Key Points |
|---|---|---|---|
| 1 | 19/08/2025 | All members | Reflected on Sprint 1, created backlog and user stories, reviewed sprint rubric, assigned tasks. |
| 2 | 22/08/2025 | All members | Planned weekend schedule, identified core feature (live games with real-time stats), confirmed TDD approach with Jest, researched API setup. |
| 3 | 26/08/2025 | All members | Discussed third-party code documentation, created ERD diagram, researched bug tracking, planned user feedback process via Google Forms. |
| 4 | 28/08/2025 | 4 members | Finalized Google Forms, reviewed outstanding tasks, progressed documentation, held pre-stakeholder review. |
| 5 | 01/09/2025 | 4 members | Reviewed stakeholder feedback, addressed urgent testing needs, divided code coverage tasks, set 25% coverage target. |
Supporting Document
All detailed sprint planning and meeting notes are maintained in this shared document:
Google Doc — Sprint 2 Planning and Notes