Feature Deep-Dive: Defining the event joining flow and user profiling.
Architecture & Database Design: Discussing data integrity, ratings, and API documentation.
Testing Strategy & QA: Determining the internal testing workflow.
Team Competency Assessment: Sharing individual backgrounds and technical expertise to align roles.
💬 Discussion Summary
Benchmark Analysis: Competitors such as Kide.app, GetYourGuide, and Meetup were analyzed to identify potential core features and our value proposition.
Map Integration:Leaflet is being considered as a primary candidate for map-based event discovery.
Join Request Logic: A Pending Request system is proposed to maintain event quality. Instead of an open-join policy, a system where organizers can approve requests could be implemented to prevent spam, with the option to toggle this for smaller events.
User Profiles & Reputation: User profiles could feature participation history to build trust. A Rating System is being considered for organizers; metrics such as cancellation rates might be used to reflect reliability and influence their overall rating.
Privacy Levels: The possibility of categorizing events into three tiers—Public, Private, and Protected—was discussed to provide better access control.
API Documentation: To ensure seamless communication between Backend and Frontend teams, using Swagger for API documentation and clear endpoint definitions is recommended.
Testing Policy: Rather than a dedicated QA team, a collaborative testing approach is suggested. Team members could perform manual testing during usage and report bugs as Issues to optimize human resources.
🚀 Action Steps
@kaanunsel: Update Requirements page based on the elicitation results. (Deadline: 19/02)
@sevdepekkose: Create a dedicated Use Case Scenarios page. (Deadline: 19/02)