Sprint 3 — Client Meeting
Date: February 20th, 2026
Engagement Metrics Discussion
We discussed how to define and measure "involvement" or "engagement" and success within the platform.
Success should ideally be reflected by a higher number of events, especially smaller community-driven events.
Currently, large alumni events (e.g., the annual event) are not registered in the app, so the focus should be on smaller events organized within the platform.
Number of attendees can serve as a key success metric.
A potential limitation was noted: users may see and attend an event without signing up in the app, which may affect the accuracy of attendance metrics.
Possible engagement indicators include:
- Users creating events
- Users signing up for events
- Profile visits
- User interactions such as button clicks within the app
Additional feature idea:
- Waiting lists for events with a limited number of participants.
User Profile
Discussion about the structure and functionality of user profiles. Final design details will be further defined in the next meeting.
- Profiles may include labels such as graduation year.
- Profiles may also include achievement badges (e.g., attended 5 events, organized an event).
- One potential improvement is to use the graduation field from the university database to verify alumni automatically.
- The system should also support users who are not alumni, such as employees or external participants (e.g., friends of the community), allowing them to register without requiring a graduation year.
User Validation
- The Digital Profile is currently used to manually verify that a person exists and has graduated.
- The current manual validation process may allow impersonation, which is a potential risk.
Event Information
- Events should include contact information for the event creator (e.g., Telegram alias).
- Events may also include a cost field if participation requires payment.