Customer Meeting 1 - bounswe/bounswe2026group9 GitHub Wiki
📅 Date - Time: 18.02.2026 - 20:00 📍 Location: Zoom ⏳ Duration: 40 🗣️ Communicator: İbrahim Fırat 📝 Note Takers: Can Emir Bora, 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
- 0-20 min - Ask the must-ask questions and obtain clear answers. 1.1.1, 1.1.3, 1.2.1, 1.2.2, 1.3.1, 2.1.1, 2.3.1, 3.1.1, 3.1.2, 3.3.1, 4.1.1, 4.2.1, 4.3.1, 5.1.1, 5.2.1, 5.3.1, 6.1.1, 6.3.1, 7.3.1, 9.1.1, 9.2.1, 10.2.2
- 0-30 min - Take structured notes based on the customer’s needs and preferences, and derive concrete action items from these notes.
- 20-29 min (it could be in 0-20 min also) - Ask relevant follow-up questions during the discussion to expand and refine the must-ask question set.
- 29-30 min - If the customer agrees, schedule the date and time of the next meeting in last two minutes.
🗣️ Discussion Notes
1.1.1 There is no restriction. Everyone who uses the application can do it. This applies to all possible events; it doesn’t have to be a professional event organization company.
1.2.1 The location can be anywhere, but we can start small-scale first.
1.2.2 No online events. We generally need physical locations. Optionally, we can support online meeting-type events.
1.3.1 Events that are close in time and location should be prioritized and shown first.
2.1.1 Requirements for an event: title, description, category must be provided; start/end time, duration, location, coordinates, image. There can be comments under the same event. Optionally, required items can be added. Optional fields like health condition requirements can also be included.
2.3.1 No extra requirement other than 18+.
3.1.1 Roles: registered user, guest, publisher, admin, guest. Publisher = registered user.
3.1.2 If not registered, the user can only view events and their details. People who showed interest in a host’s previous events should be able to be notified about new events, but this is a nice-to-have feature.
3.3.1 Modes: public, private. Private events should be visible to everyone, but details should not be shown.
4.1.1 If GPS can be used directly, the map will look better on mobile. But it may cause technical issues. If not possible, there should be a Default View set to a preselected area of the map. This view should also be changeable based on user preference. Events should be shown both as a list and on the map.
4.2.1 VERY TECHNICAL. Methods like selecting the nearest location and choosing a radius, or always showing the nearest first 5 events, can be tried.
4.3.1 A custom time window with definite start-end must be included.
5.2.1 Sort modes: distance, category, time. Create a list based on these and show the top 10 first.
6.1.1 Commenting under an event must definitely exist. Other users should be able to see them. Peer-to-peer messaging maybe later (host-user).
6.3.1 There should be a host page with contact information, events, and ratings. Host rating and user rating should be shown separately, because host = registered user.
7.3.1 Notifications must always exist. When there is a change or cancellation, we should always send them.
Saving/bookmarking an event can be done. A post-event “did you like it?” notification can be sent. These are also NICE TO HAVE THINGS. An event ending is always determined by the end of its duration.
9.1.1 Yes, but not everything. Let’s note this as a scenario: in some cases the entire event is cancelled and a new one is created; in other cases it can be directly edited.
9.2.1 Past scheduled events can be updated. An optional attendee limit can exist; then we add something like full, sold out, etc.