Sprint Retrospectives 2.2 - FEUP-MEIC-DS-2025-26/madeinportugal.store GitHub Wiki
Sprint 1
What went well
- Jumpseller integration is now fully operational.
- The frontend migration to React was completed successfully.
- Development pipelines were built and are functioning as intended.
What to improve
- Automated tests stopped working after Jumpseller integration and need to be readjusted in the next sprint.
- The Google Cloud deployment could not be completed before the end of the sprint and must be finalized in the next one.
Others
- The information regarding Jumpseller was not publicly available, which meant we had to rely on another group and this caused delays.
- Furthermore, we only gained access to the assessment parameters very close to the end of the sprint, as they were not communicated during lectures or practical sessions, and we only noticed their publication on Moodle at the last minute. For the next sprint, it will be essential to ask the lecturers to align their expectations with us more clearly, in order to avoid delays and ensure greater transparency and efficiency in teamwork.
Sprint 2
What went well
We successfully reviewed the Infrastructure Wiki and identified the necessary repositories for the integration with the main website:
- We updated the routes.json file to successfully connect our deployment to the main site (View File).
- We cloned the frontend repository (https://github.com/FEUP-MEIC-DS-2025-26/MIPS-Frontend-Host-Module-Federation) and created the feat/product-page branch to add our frontend, as seen in the commit history (https://github.com/FEUP-MEIC-DS-2025-26/MIPS-Frontend-Host-Module-Federation/commits/feat/product-page/).
- Despite challenges, we managed to also work on the Pub/Sub and integrate the reviews microservice.
What to improve
- We faced some external communication issues and there was a lack of clarity regarding specific details on how the integration with the main website should proceed, leading to unnecessary frustration, so better exposition of instructions would be appreciated.
- We need to streamline the integration process to avoid the "headaches" encountered during this iteration.
Others
- We encountered technical setbacks beyond our control, including a GitHub Actions outage and unexpected modifications by others to the dummy products in the Jumpseller database.
- We are preparing for the next phase, where we expect to perform further integrations with additional microservices of other teams.