Weekly Meeting #1 Report

Date: 18.02.2026

Time: 20:00 - 21:00

Participants

• Ali Akkaya ✅
• Bora Aydemir ✅
• Ömer Belemir Delier ✅
• Arif Evren ✅
• Ulaş Sertan Kemeç ✅
• Ekin Kılıç ✅
• Baran Önder ✅

Agenda

1. Review of Lab 1 Feedback and GitHub repository standardization.
2. Preparation of Elicitation Questions for the upcoming Customer Meeting.
3. Conducting the initial Customer Meeting.
4. Brainstorming potential system roles and actors in preparation for Lab 2.

Discussion Items

• Lab 1 Feedback & GitHub Workflow: We extensively reviewed the TA feedback from Lab 1. The team agreed to establish a strict GitHub workflow. Moving forward, all tasks must use a standardized Issue Template (including descriptions, tasks, and deliverables). Every issue must be linked to the GitHub Project board with appropriate tags and properly closed upon completion. We also discussed restructuring the Wiki Home page and ensuring all individual contributions are traceable via issue links.

• Elicitation Questions & Customer Meeting Summary: We reviewed and finalized our list of elicitation questions to ensure we could extract clear "Must-Have" vs. "Nice-to-Have" boundaries. Following this preparation, we held our first Customer Meeting. During this brief session, we successfully clarified the MVP scope (focusing on campus environments) and identified the target audience.

• System Roles Brainstorming (Pre-Lab 2): Anticipating the requirements for Lab 2, we held a preliminary brainstorming session regarding the core actors of our system. We identified key user roles—such as disabled users navigating routes, voluntary contributors reporting obstacles, and municipality officials tracking issues—to serve as a foundation for future scenario drafting.

Action Steps

• Bora Aydemir: Create the standard GitHub Issue Template and configure the project Kanban board.
• Bora Aydemir: Update the Elicitation Questions Wiki page with the newly categorized items discussed prior to the customer meeting.
• Ulaş Sertan Kemeç: Prepare and document the official Customer Meeting Report based on the outcomes discussed.
• All Team Members: Review the core concepts and identified user roles from the Customer Meeting to be prepared for the upcoming Lab 2 session.