Meeting Minutes (Meeting with TA)

Date: 2026-03-04
Time: 09:45 - 10:20
Location/Platform: In-person(KHRA L1-350)
Facilitator: Aditya

Attendance

Name Present (✅/❌) Notes
Aditya ✅
Pragya ✅
Prajin ✅
Smriti ❌
Mustafa ✅
Ashwin ✅
Salaar ❌

Discussion & Agenda

Sprint 2 feedback

  • good overall
  • lost marks:
    • Demo timing
    • late for demo(setup within 5 min)
    • 2% penalty
  • address ta feedback: full
  • system architecture: full
  • UML: lost marks(mentioned in previous TA meeting)
    • do UML off of sprint 1
    • 1 mark off
  • design is planned, functionalities: lost 2 marks
  • progress: full
  • gh practices: good
    • branches, PR: good
    • self hosted runner,
    • codeQL checks
    • branch rules
    • code structure, comments,
    • testing: excellent
    • test coverage
  • project plan, storymap, velocity, docs stuff, detailed github issues, labels, assignees: all good
  • meeting minutes: good
  • sprint3 attendance: good but sprint3 bad
  • team contribution: good
  • demo: troubleshoot so lost lost 2 marks
  • scrum roles defined: full
  • sequence diagram: super good(liked the supabaseauth, supabase)
  • rtm:
    • remove "requirementId"
    • rename "test name" to "Test Description"

  • total marks: 95/100

  • check detailed rubric sprint 2 from course page

Questions for the TA

  • Consider accessibility in sprint3

    Accessibility is considered and described in the docs
    (e.g. colors pass contrast check, see https://accessibilityaid.com/free-tools/colour-contrast-checker)

    • TA answer:
      • automated script to test accessibility
      • mention in docs

  • using expo go, apk required or not?, testflight $99/year apple developer account subscription required

    Project is deployed to a non-local (production-like) environment,
    and acceptance tests are executed against the deployed system (not a local development instance)

    • TA answer:
      • do the apk in workflow
      • store in storage bucket, give non RLS link for TA to be able to download

  • confirm if we did labels properly done or not

    • TA answer:
      • good
      • assign people, milestones to github for sprint 4

Sprint 3 Expectations

  • UI/UX
    • give concrete hueristic examples
      • eg: state of app is shown to user:
      • instead of hanging, show loading icon
  • accessibility
  • colorblind, screenreaders
  • subsection in docs for all these parts(check sprint 3 rubric)
  • work on this better this sprint 3:
    • demo
    • UML(go to sprint 1 UML)
  • UI UX: visibly aligned, not pixel level UI consistency

sprint 5:

  • manual
  • deployment docs

Decisions Made/Next Steps

  • address sprint 2 feedbacks

References/Attachments(optional)