Sprint 10 - Mentor meeting

Agenda

Mentor flagged our project as one of three he's concerned about — not clear where we're targeting
Dashboard activity dropped sharply after MoSP and only picked up recently
Team admits they "stopped working for a while" after MoSP and lost momentum
Hilali stuck for over a week on the GitHub runner not pulling jobs on the third VM — should have asked for help sooner
Email/SMTP password issue with university IT: better to physically visit the IT person than wait on Telegram tickets
General point: if a problem takes more than ~1 week, escalate or delegate

Estimated cost of refactoring Flutter → React: ~30-40 hours, plus high risk of new bugs
Refactoring would only pay off if we had ~20+ mobile tasks coming up, which we don't
Decision: keep Flutter for this semester; refactoring would be overkill given the small mobile workload
This justification will go into the end-of-semester presentation

We don't really do formal retros; reflection happens informally and rarely produces concrete improvements
The last full team meeting only happened because we forced it — meetings have been getting skipped
We prioritize other courses/jobs over the project too often
Tasks get assigned but completion isn't enforced — "no consequences" if someone doesn't finish
Agreed rule: every member commits to ≥10 hours of clearly-described tasks per sprint, tasks split if longer than ~3 hours
Whoever doesn't complete their committed tasks buys pizza for the team

Date: May 12th, all 5 mentors will be grading
Format: 20 min presentation + 20 min Q&A + 5 min client feedback (45 min total)
Clients will be invited; mentor will share criteria document
Plan should reflect changes from the original — show how it adapted, not just what it is now
Peer evaluation form will be shared in May, completed before the presentation