Stakeholder Interaction Log

Date : 27 August 2025

Time : 19h15 - 20h00

Attendess: Joshua Williams, Lehlohonolo Tosa , Mohau Makunyane, Kwezi Mudacumura , Bohlale Mabonga

Stakeholder Name: Rohan (Tutor)

Method of Interaction: Online Meeting. ( On Discord)

Agenda Items Discussed:

1. Feature Implementation Deadline

   • All features must be implemented by next week. However, the actual score will depend on the rubric, so even if all four features are not fully implemented, we may not achieve 100%.
   • Key Requirements:
     • Features don’t need to be perfect but should be aesthetically pleasing.
     • Ensure that features have non-severe bugs or are at least functional with minimal issues.

2. UI Testing & Documentation

   • Test all UI elements thoroughly to ensure proper functionality.
   • Test all API endpoints to confirm that they are working as expected.
   • Document all tests: Describe how to run them, what to test, and their expected outcomes.

   3 .API Issue from Last Week

   • Resolve the API issues from last week.
   • Do not use Firebase libraries that involve API calling and fetching data.

   4 . API Availability for External Usage

   • Ensure that the API is available for external usage and can be integrated with other projects.
   • Integration Testing:
     • Ideally, integrate with the Spot Stat Tracker project.
     • Test calling their API; if the API is down, return a message like: “API Unavailable.”

   5 . Feedback on Website & User Reviews

   • Have people review the website and provide feedback.
   • Document all feedback and make sure to implement useful suggestions.

   6 . Use of Notion

   • Continue using Notion and regularly update it to track project progress, tasks, and documentation.

     7.Bug Tracker & GitHub Issues

• Ensure that the bug tracker is functional and that GitHub issues are being actively used to track bugs and feature requests.
• Be prepared to explain how GitHub issues are used and show examples.

8.DB Schema & Code Documentation

• DB Schema: Be ready to explain the schema design and why certain choices were made.
• Code Documentation: Ensure that critical sections of the code, like the Post API, are properly documented.

9 . Testing Review & Demonstration

• Prepare to run tests during the next meeting to demonstrate that all required tests are in place and functioning.
• Stakeholder may go through the tests and ask questions on the testing process.

Action Items:

1. API Fixes: Rohan told us Resolve the issue from last week with the Firebase libraries and ensure API accessibility for external use,i.e other groups.
2. Implement Features: Rohan empashised that we Focus on deleloping all core feautres by sprint 2
3. UI & API Testing: Test all elements thoroughly and document the process.,Rohan said he will a
4. Website Feedback: Collect feedback from users, document their comments, and implement valid suggestions.
5. Notion Updates: Regularly update the project progress and document meeting notes in Notion, as per rubric
6. GitHub Issues: Continue using GitHub issues for bug tracking and be ready to demonstrate this during the next meeting. Rohan said that GitHub Issues is fine
7. DB Schema Explanation: Be prepared to explain the DB schema and your choices during the sprint .