Repository navigation
The Sprints
For Sprint 1, a velocity of 63 story points was estimated. It included 69 tickets on the project development board and 12 user stories on the project management board.
The database has been planned and implemented. Basic setup tasks have been completed, such as implementing PrimeNG UI elements. Additionally, the mockup has been further adjusted. In the backend, functions for creating users, login, authentication, and creating events have been fully implemented. In the frontend, user login is also possible.
So far, ONE user story has been fully implemented.
The functions from the backend, such as Create Event, still need to be implemented in the frontend. Sockets also need to be implemented. Displaying events must be enabled in both the backend and frontend for all events, including those created by the user and as a guest. This requires a detailed view as well as a card view. Additionally, users must be able to register for events.
All tickets related to the backend are ready, such as reading events (your own and joined), event details, as well as creating requests and joining events. I am The login function was further adapted to the frontend and sockets were implemented. Navbar and footer were mostly added. Creating events and creating users were quickly and completely implemented. Multilingualism was also implemented in the frontend. Legal texts such as legal disclosure, privacy policy and terms and conditions were written.
So far, ONE user story has been completely implemented.
The Create User and Event functions must be fully implemented in the frontend. Reading created and joined events must also be possible in the frontend. The details page must be completed and the option to join/request an event must be available. The legal texts must also be available on the website.
Registration has been fully implemented. The event details page is displayed in the frontend and you can register for events/send a request. The navbar has been revised and the layout adjusted. Terms and conditions, legal notice and data protection have also been added. A user can now see all the events they have created and registered for. The next sprint has been planned.
All user stories have been implemented.
For Sprint 2, a velocity of 62 story points was estimated. It included 67 tickets on the project development board and 13 user stories on the project management board.
Bugs and styling from the last sprint have been improved and fixed. The mockups for tickets from Sprint 2 have been implemented. Logout has been fully implemented, as has the My-Space page. In the backend, the logic of event requests has been fully implemented, as well as the viewing and editing of user data. You can also read the event participants and host data. The details page and registration for an event in the frontend are also visually blocked if you are not logged in.
The functions implemented in the backend must be implemented in the frontend (requests, profile). Lists and surveys must be implemented in the backend and frontend, as well as the tags for events and users. Unsubscribe from an event must be implemented.
The routing for the event detail page has been reworked. Lists can be created and displayed. The event status is displayed in the corresponding areas. The upcoming events are displayed on the home page. The profile can be viewed and edited. Event requests can be sent and accepted.
The complete logic for lists and surveys is implemented in the backend.
Surveys and lists must work in the frontend. Tags should be able to be specified for events. Event participants and host should be displayed.
Lists and polls have been fully implemented (CRUD). Tags have also been fully implemented in the profile and during event creation. Host and participant information is displayed in the event details. The login/registration page has been redesigned. Sockets have been implemented.
All user stories have been implemented.
Sprint 3.
For Sprint 3, a velocity of 92 story points was estimated. It included 85 tickets on the project development board and 18 user stories on the project management board.
The chat has been fully implemented in both the frontend and backend. Friends functionality has been implemented in the backend, and adding as well as viewing profile pictures has also been completed. The design for private events with invitations has been created in a mockup, and the functionality has been partially implemented in the backend. Creating QR codes for friends is also possible.
So far, TWO user stories have been fully implemented.
The functionality for event invites and adding friends via QR code needs to be fully implemented. Event images must be correctly uploaded and displayed. The filtering functionality for events must be completely implemented in both the frontend and backend. Notifications for the website need to be fully implemented. The For-You page, including its algorithm, needs to be planned and implemented. The app must be operational and properly deployed on a server.
Event invitations have been almost fully implemented. Filters have been implemented in the backend and started in the frontend. The For-You page has been implemented. Deployment has also been completed. Event images can now be uploaded. It is possible to add friends using an invitation link and scan a QR code with the camera directly on the website.
Event invitations need to be properly displayed in the frontend. The filter functionality must be finalized in the frontend. Event images should be correctly displayed. Notifications need to be implemented for chat messages and event requests. The app must be fully implemented. Bugs need to be identified and resolved to ensure smooth functionality.
Event invitations have been fully implemented. Filters have been fully completed. Event images are now displayed on the website. The documentation has been expanded and translated, and the README has been improved. Numerous bugs have been fixed.
The last steps include completing the two videos and finalizing the documentation. Additionally, all remaining bugs need to be fixed to ensure the project is polished and fully functional.