Skip to content

Team Meetings

Jump to bottom
vaibhav jain edited this page Mar 31, 2025 · 16 revisions

First Meeting

Project Kickoff Meeting Minutes

Date: Tuesday, 28 January, 2025

Time: 5:00 pm during lab hours

Location: NRE 2-001

Attendees:

  • Divit Batra
  • Jimi Lin
  • Mekha George
  • Vaibhav Jain
  • Songrao Fang
  • Gurkaranvir Kaur
  • Teaching Assistant (TA)

Purpose

The primary objectives of the meeting were to allocate tasks for Project Part 0 and meet with our TA.

Task Allocation

  1. Divit Batra
  • Project Repository: Created the initial project repository on GitHub.
  • Project Board: Set up the project board.
  • CODEOWNERS File: Created the CODEOWNERS file and added everyone's Github username to it.
  1. Jimi Lin
  • README Documentation: Composed and added the README file to provide an overview of the project.
  • License Update: Incorporated our team name into the LICENSE.md file.
  1. Mekha George
  • License Management: Added the LICENSE file.
  • Issue Resolution: Resolved an issue on the project board related to the team number assignment.
  1. Vaibhav Jain
  • GitHub Wiki: Created the GitHub Wiki for the repository and populated it with all relevant project information to serve as a centralized documentation hub.
  1. Songrao Fang
  • Android Project Initialization: Initialized an empty Android project within the /code directory to establish the structure for development.
  1. Gurkaranvir Kaur
  • Team Support: Assisted all team members in completing their assigned tasks, ensuring smooth progress and addressing any challenges encountered.

Everyone also added their names and CCID's to the README file.

Conclusion

The initial meeting successfully laid the groundwork for the project. The team demonstrated effective collaboration and commitment to achieving the project objectives.

Second Meeting

Project Part 2 Meeting Minutes

Date: Tuesday, 4 February, 2025

Time: 5:00 pm during lab hours

Location: NRE 2-001

Attendees:

  • Divit Batra
  • Jimi Lin
  • Mekha George
  • Vaibhav Jain
  • Songrao Fang
  • Gurkaranvir Kaur
  • Teaching Assistant (TA)

Purpose

The primary objectives of the meeting were to allocate tasks for Project Part 2.

Task Allocation

Group was split into 2 teams to maximize work

Group 1: Mekha, Jimi, and Songrao

  • Focused on UI/UX Design (Front-End).
  • Designing and prototyping the user interface.
  • Mapping UI elements to corresponding user stories.

Group 2: Divit, Vaibhav, and Gurkaranvir

  • Focused on GitHub Issues, Milestones (Backend) and CRC cards.
  • Refining and finalizing the backlog page.
  • Estimating story points and assigning risk levels to each user story.
  • Building initial CRC (Class-Responsibility-Collaborator) cards for key classes.
  • Updating the GitHub Wiki with new information and meeting notes.

Conclusion

We decided to complete our tasks by the next meeting and keep a check on each other's progress.

Third Meeting

Date: Tuesday, February 11, 2025

Time: 5:00 pm – 8:00 pm

Location: NRE 2-001

Topic: Project Part 2 Finalization

Attendees:

  • Vaibhav Jain
  • Divit Batra
  • Jimi Lin
  • Gurkaranvir Kaur
  • Mekha George
  • Songrao Fang
  • Teaching Assistant (TA)

Purpose

The purpose of the meeting was to finalize everything for the project part 2 submission and check up on each others's progress.

Tasks Allocation

No tasks were allocated. Each member had done their part successfully and we were 90% done with the project part 2 submission.

Tasks Completed

  • The UI Mockups and Storyboard sequence was complete.
  • The backlog page was ready.
  • The CRC cards had been made.

Tasks Remaining

  • The Github wiki was left to be updated.

Conclusion

Team was happy with the progress that has been made :)

User Story Feature Completion Meeting Notes

Date: March 18, 2025
Time: 5:53 PM – 6:10 PM
Location: NRE 2-001

Attendees

  • Divit Batra
  • Vaibhav Jain
  • Jimi Lin
  • Mekha George
  • Songrao Fang
  • Gurkaranvir Kaur
  • (Meeting organized by TA)

Purpose

This meeting was convened to confirm and document the assignment and completion of specific user story features for the project. The team reviewed the user story responsibilities and ensured that each member’s contributions were properly tracked.

Task Assignments & Completed User Story Features

  • @Vaibhav Jain

    • US 04.02.01: Filter mood history list to show only mood events that occurred in the most recent week.
    • US 04.03.01: Filter mood history list to show only mood events with a particular emotional state.
    • US 04.04.01: Filter mood history list to show only mood events whose "reason why" text contains a given word.

  • @Mekha George

    • US 05.04.01: Filter mood following list to show only mood events that occurred in the most recent week.
    • US 05.05.01: Filter mood following list to show only mood events with a particular emotional state.
    • US 05.06.01: Filter mood following list to show only mood events whose "reason why" text contains a given word.

  • @Gurkaranvir Kaur

    • US 05.01.01: Ask another participant to follow their most recent mood event profile.
    • US 05.02.01: Grant another participant permission to follow my most recent mood event.
    • US 05.02.02: View all users who have requested to follow me.
    • US 05.03.01: View as a list the 3 most recent mood events of the participants I am granted to follow, sorted in reverse chronological order.

  • @Songrao Fang

    • US 06.01.01: Optionally attach my current location to a mood event.
    • US 06.02.01: See a map of the mood events (showing their emotional states) from my filtered mood history list that have locations.

  • @Jimi Lin

    • US 06.03.01: See a map of the mood events (showing their emotional states and the username) from my filtered mood following list that have locations.
    • US 06.04.01: See a map of the most recent mood event of every participant I am following (showing their emotional states) if the event has a location and is within 5 km of my current location.

  • @Divit Batra

    • US 01.07.01: Post private or public mood events (for personal journaling or public sharing).
    • US 05.07.01: Comment on a specific mood event.
    • US 05.07.02: View all comments on a given mood event.
    • US 07.01.01: Add, edit, or delete a mood event while offline, with synchronization once connectivity is restored.

Conclusion

The meeting successfully recorded the completion of assigned user story features by each team member. All assignments were confirmed, ensuring that every aspect of the project’s requirements is covered ahead of the final demonstration.

Final Development & Documentation Meeting

Date: Thursday, 26 March, 2025
Time: 5:00 pm during lab hours
Location: NRE 2-001

Attendees:

  • Divit Batra
  • Vaibhav Jain
  • Jimi Lin
  • Mekha George
  • Songrao Fang
  • Gurkaranvir Kaur
  • Teaching Assistant (TA)

Purpose

This meeting focused on finalizing all development tasks, integrating TA feedback, and ensuring that the project meets the user stories and deliverables. The team reviewed the final task assignments based on the recent screenshot and user stories.

Task Allocation & Status Updates

  • Vaibhav Jain

    • Responsibilities:
      • Led the UI updates and implemented all final test cases.
      • Ensured that UI elements reflect the required emoticons, colors, and overall design as per the user stories
    • Status: Completed

  • Divit Batra

    • Responsibilities:
      • Finished and polished the backend functionalities.
      • Addressed all bug fixes and performance issues.
    • Status: Completed

  • Jimi Lin, Mekha George, Songrao Fang, Gurkaranvir Kaur

    • Responsibilities:
      • Updated Javadoc for all source files and model classes.
      • Refined Figma designs to match the UI/UX guidelines provided in the user stories.
      • Revised UML diagrams to include key attributes, methods, and design patterns.
      • Finalized the README file and compiled comprehensive meeting notes.
    • Status: Completed

Discussion Points

  • User Stories Verification:
    The team verified that all user stories, from mood event creation (US 01.01.01) to offline behavior (US 07.01.01), have been addressed in the current build.

  • Documentation & Code Quality:
    Reviewed consistency in coding conventions, Javadoc comments, and adherence to design patterns as outlined in the project requirements.

  • Test Cases:
    Confirmed that all tests are runnable and realistic, ensuring the application’s functionality meets the acceptance criteria.

Conclusion

All development and documentation tasks have been completed as per the deliverables. The project is now ready for the final demonstration.

Clone this wiki locally