Sprint 2 — Mentor Meeting
Date: February 17th, 2026, 17:00
Agenda
- Discuss the requirements engineering approach
- Discuss elicited requirements
- Discuss current status regarding migration and development
- Get advice on next steps
Requirements Engineering Approach
- Decide on criteria and their priorities together with Anna.
- Clarify what matters more — events count or number of people involved?
- Define clear metrics with specific numbers and derive a success threshold:
- Example: 10 events with at least 3 different attendees each.
- Or use a large event (e.g., alumni reunion at uni) as a milestone marker.
- Document use cases with preconditions, postconditions, and alternative flows; define misuse cases.
- Use diagrams — especially use case diagrams (high priority).
Requirements
- Clarify what types of events exist.
- Determine which events and engagement types are counted.
- Requirements must be specific and contribute to a clear understanding of the project.
- Include requirements inherited from the previous team and build on top of them.
- Consider what information is required per event (e.g., host contact info).
Current Status
- Migration status discussed, along with the SSH access issue outside the university network.
- No SSH access outside the campus remains a blocker.
Next Steps
- [ ] Consider starting the project from scratch as an option.
- [ ] Consider migrating to the university GitHub.
- [ ] Assess whether the current product aligns with the team's goals.
- [ ] Define and document a workflow methodology (e.g., Agile) with roles and responsibilities (high priority).