📄 Stakeholder Interaction Log

Stakeholder Name: Rohan (Tutor)

Role: Academic Supervisor / Product Advisor

Date of Interaction: [12 August 2025]

Facilitated By: [Rohan]

Method of Interaction: In-Person Meeting.

🧠 Purpose of the Meeting

To review the current progress of the project, clarify assessment rubric expectations, and align team deliverables with stakeholder (tutor) feedback for the upcoming sprint and to identify hidden features.

🗣 Summary of Discussion

✅ General Expectations & Guidelines

• Sprint Attendance:

  Attendance is compulsory for every sprint. All team members must be present and actively participate in meetings and reviews.

• Recording Policy:

  The tutor prefers written notes over recorded meetings. Teams should focus on real-time documentation and note-taking to show engagement.

🎯 Project Scope & Direction

• It is acceptable for the system to focus on one sport only (e.g. football), provided the features are complete and well-executed.
• Tutor acknowledged that depth of functionality is more important than breadth.

📌 Feature & Rubric Alignment

• The tutor reviewed the assessment rubric with the team and explained each feature in detail.
• The following were highlighted as non-negotiable technical requirements:
  • Ability to Create, Read, and Update from the database (minimum CRUD functionality).
  • Clear implementation of match setup, even if simulated or partially handled due to external API constraints.
  • Working authentication system and role-based logic (e.g., admin vs. user).

📦 Version Control & Release Strategy