-
Notifications
You must be signed in to change notification settings - Fork 0
Weekly Meeting 7 (11.04.2026)
Muhammet Sami Çakmak edited this page Apr 11, 2026
·
2 revisions
- Topic: MVP milestone review, addressing feedback, and writing the MVP report
- Date: 2026-04-11
- Time: 19:45 - 20:35
- Location: Google Meet
- Scribe: Muhammet Sami Çakmak
| Name | Status |
|---|---|
| Burak Öğüt | Present |
| Amin Abu-Hilga | Present |
| Muhammet Sami Çakmak | Present |
| Övgü Su Afşar | Present |
| Mehmet Bora Sarıoğlu | Present |
| İbrahim Kayan | Present |
| Beratcan Doğan | Present |
- Reviewing the overall status of the MVP Report.
- Addressing and completing the missing parts in section
D6.4 Testing. - Addressing and completing the missing parts in section
D6.5 Planning and Team Process. - Final check on
D7. Individual Contributionsformats for all members.
- MVP Report Status: We reviewed the current draft of the MVP report. While the project status (D6.1), deliverables (D6.2), and requirements (D6.3) were mostly complete, the team identified that the testing and team process sections required more detailed documentation.
- D6.4 Testing Completion: We discussed the testing strategy and execution. The team aggregated the test results for the Backend API, Web App, and Mobile App. We agreed on how to format the "Impact Analysis" by listing specific bugs detected and how our test coverage ensured the MVP's readiness.
- D6.5 Planning and Team Process: We evaluated our team's performance and agile process during the MVP phase. We decided to include specific screenshots of our GitHub Projects board, issue tracking, and PR reviews to visualize our workflow and collaborative efforts.
- D7 Individual Contributions: Reminded all members to adhere to the agreed-upon template, ensuring that every code-related issue and PR includes a brief explanation and links to the relevant test files.
-
Decision 1: The
D6.4 TestingandD6.5 Planning and Team Processsections have been collaboratively filled out, finalized, and approved by the team during the meeting. - Decision 2: All test execution reports (HTML/XML formats) will be hosted within the repository, and their relative links will be added directly to the D6.4.2 section.
-
Decision 3: Every team member must finalize and push their
D7 Individual Contributionssection before the final MVP release deadline.
Next Meeting Date: 2026-04-18
Team Members
- Lab 1 Report (12/02/2026)
- Lab 2 Report (19/02/2026)
- Lab 3 Report (26/02/2026)
- Lab 4 Report (05/03/2026)
- Lab 5 Report (12/03/2026)
- Lab 6 Report (26/03/2026)
- Lab 7 Report (02/04/2026)
- Lab 8 Report (18/04/2026)
- Lab 9 Report (30/04/2026)
- Lab 10 Report (07/05/2026)
- Weekly Meeting Notes Template
- Lab Meeting 1 (12.02.2026)
- Weekly Meeting 1 (16.02.2026)
- Weekly Meeting 2 (24.02.2026)
- Weekly Meeting 3 (04.03.2026)
- Weekly Meeting 4 (11.03.2026)
- Weekly Meeting 5 (23.03.2026)
- Weekly Meeting 6 (29.03.2026)
- Weekly Meeting 7 (11.04.2026)
- Weekly Meeting 8 (28.04.2026)
- Weekly Meeting 9 (10.05.2026)
- Use Case Diagram 1 (New Mentor User for Mobile Scenario)
- Use Case Diagram 2 (Mentor-Mentee Matching Scenario)
- Use Case Diagram 3 (New Mentee User Scenario)
- Final Use Case Diagram
- MVP Use Case Diagram
- All Sequence Diagrams
- Sequence Diagram: Mentee Matching
- Sequence Diagram: Mentor Matching
- Sequence Diagram: Mentorship Management
- Sequence Diagram: Registration
- Sequence Diagram: Cancelling Mentorship Relationship and Auto Ban
- Sequence Diagram: Login-Logout
- Sequence Diagram: Reporting-User
- Sequence Diagram: Mentor Profile Management
- MVP Sequence Diagrams
- Test Plan & Coverage (MVP)
- Acceptance Testing Strategy
- Acceptance Tests
- Test Data Strategy
- Web Frontend Test Report
- Amin Abu-Hilga
- Övgü Su Afşar
- Muhammet Sami Çakmak
- Beratcan Doğan
- İbrahim Kayan
- Burak Ögüt
- Mehmet Bora Sarıoğlu
- Future Work (reference, not a deliverable)