Weekly Meeting 2 - bounswe/bounswe2026group9 GitHub Wiki
📅 Date - Time: 18.02.2026 - 21:30
📍 Location: Google Meets
⌛ Duration: 30 Minutes
📝 Note Taker: Muhittin Köybaşı
👥 Participants
| Member |
Participated |
| Can Emir BORA |
X |
| Emre BEKTAŞ |
|
| Mustafa KOYUNCU |
X |
| Muhittin KÖYBAŞI |
X |
| Faik İhsan SÜDÜPAK |
|
| İbrahim Fırat YOĞURTÇU |
X |
| Tuğçe YÜCEL |
|
📋 Agenda
🗣️ Discussion Summary
- Update requirements based on the customer’s answers to the elicitation questions.
- Re-structure requirements into:
- Functional Requirements
- User Requirements
- System Requirements
- Non-Functional Requirements
- Refine (narrow) elicitation questions so they are more specific and reduce the risk of an unclear / expanding project scope.
- Meeting roles rotation (reversed alphabetical order):
- Each week, two people take the roles: moderator and note-taker.
- Roles rotate weekly following the reversed alphabetical list.
- Moderator must have a clear understanding of that week’s lecture and ps topics.
- Current schedule:
- Week 3: Note-taker — Mustafa Koyuncu | Moderator — Muhittin Köybaşı
- Week 4: Note-taker — İbrahım Fırat Yoğurtçu | Moderator — Faik İhsan Südüpak
- Week 5: Note-taker — Can Emir Bora | Moderator — Mustafa Koyun
- Week 6: Note-taker — Muhittin Köybaşı | Moderator — İbrahım Fırat Yoğurtçu
- Week 7: Note-taker — Faik İhsan Südüpak | Moderator — Can Emir Bora
- …continues in the same rotation
- Create scenarios that explicitly cover and validate the finalized requirements.
- Issue tracking workflow (GitHub Projects):
- We will use Project fields to assign priority and time estimates.
- After creating an issue, ensure all required fields are filled in (e.g., priority, estimate, status, etc.).
📝 Action Steps
| Action |
Assignee |
Deadline |
| Refine The Non-Functional Requirements |
Can Emir Bora |
19.02.2026 |
| Refine The Functional (User) Requirements |
İbrahim Fırat Yoğurtçu |
19.02.2026 |
| Refine The Functional (System) Requirements |
Muhittin Köybaşı |
19.02.2026 |