Skip to main content

Sprint 2 Client Meetings

This document records Sprint 2 discussions with Harshil, including feedback and follow-up work that informed the product backlog.

03 September 2026: Sprint 2 Product Review​

Discussed​

  • The team demonstrated the current Athlora version.
  • The client reviewed the current workflow and identified issues affecting usability, presentation, reliability, and navigation.
  • The team discussed the documentation and evidence expected alongside the delivered application.

Priority Fixes​

  • Correct the injury visual on athlete tiles.
  • Repair the progression charts.
  • Repair live-weather behaviour.
  • Correct light-mode colours.
  • Add navigation controls that return users to the originating page.

Documentation and Process Follow-Up​

  • Document deployment information and the motivation for the deployment approach.
  • Maintain bug-tracker/Kanban evidence.
  • Expand testing documentation.
  • Document the database and add schema diagrams.
  • Separate third-party-code documentation from the core technology stack and reduce unnecessary dependencies.

Additional Backlog and Reliability Feedback​

  • Provide a separate team/athlete statistics view reachable from the landing page.
  • Repair athlete comparison and progression errors.
  • Ensure injuries save persistently, load reliably, and make injury dates explicitly optional.
  • Improve venue selection, event weather, participant filtering, and fixture invitation flows.
  • Support the public live-logger link/QR-code workflow with session-scoped access.
  • Investigate slow loading and refresh prompts across the application.

Decisions and Outcomes​

  • The team recorded the reported defects in the bug tracker and prioritised the injury visual, progression charts, live weather, light-mode colours, and navigation fixes.
  • The additional feature and documentation requests were recorded as backlog and documentation work; they were not treated as completed at the client meeting.
  • The Sprint 2 meeting record retains the related implementation and testing follow-up evidence.

Follow-Up​

  • Continue to validate the reported issues in both local and deployed environments.
  • Use stakeholder and user feedback alongside the bug tracker to prioritise remaining Sprint work.
  • Review larger workflow changes, including invitations and public access, with the client before removing or materially changing them.

14 September 2026: Stakeholder Feedback​

  • Harshil completed the Sprint 2 stakeholder-feedback form after reviewing the deployed application.
  • The submitted response evidence is retained in Stakeholder Feedback.

AI Declaration​

This document was created from supplied client-meeting notes with the assistance of OpenCode[openai/gpt-5.6-terra] and updated with the assistance of OpenCode[openai/gpt-5.6-terra].