Meeting Minutes 7 (Sprint 1 Planning) - JUCSE49-Mavericks/Smart-Class-Routine-Management-System GitHub Wiki
24 October 09:30 PM - 11:00 PM Discord
Sadia Hossain(SH) Umma Sumaiya Jahan(UJ) Tajrimin Mitu(TM) Trisha Sarkar(TS) Akila Nipo(AN) Rubayed All Islam(RAI)
-
We have decided to create a Product Backlog and Sprint Backlog in Trello.
-
Decided to maintain Toggl for keeping track of sprint in more detail.
-
Decided a time for the SCRUM meeting at 10 PM every day.
-
Scrum master TM.
-
Scrum Team members SH, UJ, TS, RAI, AN
-
The git commit message format will be
<< Action >> by << name >> -
Decided to create branch for every member in the format
classRoutine_memberName.
| ACTION | MEMBER(S) | DEADLINE |
|---|---|---|
| Make Product backlog & Sprint-1 backlog | SH,UJ,TM,TS,RAI,AN | 25/10/2024 |
-
🗂️ Product Backlog and Sprint Backlog: We have decided to create a Product Backlog and Sprint Backlog in Trello.
-
⏱️ Time Tracking: We will maintain Toggl for keeping track of the sprint in more detail.
-
📅 Daily SCRUM Meeting: The Scrum meeting is scheduled for 10 PM every day.
-
👨🏫 Scrum Master: TM
-
👥 Scrum Team Members: SH, UJ, TS, RAI, AN
-
📝 Git Commit Message Format: The git commit message format will be
<< Action >> by << name >>. -
🌳 Branch Naming Convention: We will create branches for every member in the format
classRoutine_memberName.
| 📝 Actions | 👤 Assigned To | 🗓️ Deadline |
|---|---|---|
| 1) View Personalized Dashboard | Jannati Tajrimin Mitu (TM) | Nov 2, 2024 |
| 2) Upload File | Sadia Hossain (SH) | Nov 2, 2024 |
| 3) Assign Course Teacher | Rubayed All Islam (RAI) | Nov 2, 2024 |
| 4) Generate Class Routine | Akila Nipo (AN) | Nov 2, 2024 |
| 5) View Class Routine | Trisha Sarkar (TS) | Nov 2, 2024 |
| 6) View Class Representative Information | Umma Sumaiya Jahan (UJ) | Nov 2, 2024 |
📝 Task:
➡️ Display a personalized dashboard for each role (teacher, student, staff, superuser).
➡️ Ensure users are logged in/registered before access.
➡️ Conduct unit testing and follow coding standards.
➡️ Add necessary documentation.
➡️ Conduct unit testing, follow coding standards and include thorough documentation.
👤 Assigned to: Jannati Tajrimin Mitu (TM)
🗓️ Deadline: Nov 2, 2024
📝 Task:
➡️ Store various information (departments, students, teachers, etc.).
➡️ Choose accepted file formats (.pdf, .csv, .xml).
➡️ Add a user-friendly upload button.
➡️ Configure server for secure storage.
➡️ Handle errors and set permissions.
➡️ Conduct unit testing, follow coding standards and include thorough documentation.
👤 Assigned to: Sadia Hossain (SH)
🗓️ Deadline: Nov 2, 2024
📝 Task:
➡️ Enable Super User to assign teachers to courses by uploading a CSV file.
➡️ Ensure prerequisites for course uploads are met.
➡️ Provide error handling for incorrect formats and upload failures.
➡️ Conduct unit testing, follow coding standards and include thorough documentation.
👤 Assigned to: Rubayed All Islam (RAI)
🗓️ Deadline: Nov 2, 2024
📝 Task:
➡️ Design a frontend interface for inputting routine parameters.
➡️ Implement logic based on room availability and teacher preferences.
➡️ Ensure smooth API interaction between frontend and backend.
➡️ Conduct unit testing, follow coding standards and include thorough documentation.
👤 Assigned to: Akila Nipo (AN)
🗓️ Deadline: Nov 2, 2024
📝 Task:
➡️ Implement a search bar for viewing class routines.
➡️ Add filtering options based on routine type.
➡️ Ensure keyword-based search functionality.
➡️ Conduct unit testing, follow coding standards and include thorough documentation.
👤 Assigned to: Trisha Sarkar (TS)
🗓️ Deadline: Nov 2, 2024
📝 Task:
➡️ Add a search bar for Class Representative (CR) information.
➡️ Implement filtering options by department, semester, and name.
➡️ Ensure accurate keyword-based search functionality.
➡️ Conduct unit testing, follow coding standards and include thorough documentation.
👤 Assigned to: Umma Sumaiya Jahan (UJ)
🗓️ Deadline: Nov 2, 2024
✔️ Followed coding standards and guidelines.
✔️ Unit tests are implemented and passed successfully.
✔️ Code is reviewed by team members.
✔️ Code is pushed into respective branches on GitHub.
✔️ Functionality is demonstrated and meets acceptance criteria.
The retrospective meeting is scheduled for November 2nd to review the sprint's performance, including successes, areas for improvement, and potential adjustments for the upcoming sprint, in collaboration with the supervisor.
We will ensure regular communication among team members through daily scrum meetings and discussions on Discord. This ensures seamless progress and fosters collaboration throughout the sprint duration.