Sprint Retrospectives 3.3 - FEUP-MEIC-DS-2025-26/madeinportugal.store GitHub Wiki
Sprint Retrospectives
Sprint 1
Retrospective
In this sprint the team sucessfully developed most of what was necessary for a large part of its section of the product backlog, including a product classification system (with no division by category yet), the review system, which includes the overall product classification according to the average of the reviews, and a way for a user to see how many loyalty system points they have.
On the other hand, the overestimation of how many PBIs could be finished made it so that the effort was distributed, leading to the team being unable to conclude a large part of the PBIs in the sprint backlog and the non-standardization of the frontend elements of each feature.
We also consider that it's important to integrate the app with Jumpseller (via their API) and deploy the app as cloud based services to make it accessible to end users and other Made In Portugal microservices.
In the next sprint we intend to fix the issues mentioned above, taking a more manageable workload and having the project deployed on the Google Cloud. We also intend to have better integration with other parts of the broader project to ensure a coherent development of the final product, mainly with the use of the Google Pub/Sub infrastructure.
Project Board
Sprint Beginning
Sprint Ending
Sprint 2
Retrospective
In this sprint the team focused on integrating our microservices with other teams working in the same value areas, deploying them in the frontend host website and integrating the app with the Jumpseller API. The team suceeded in this, making the current progress properly integrated and available in the madeinportugal page.
The focus on integration unfortunately took an additional ammount of effort that lead to the team not being able to complete the sprint backlog. The commit titles and descriptions were also insuficiently descriptive and standardized, which might make the code harder to maintain in future sprints.
In future sprints we must consider the ways in which integration might affect our workload in order to prevent further overestimations of how many PBIs the team can handle and we should define a standard, descriptive way to write commit titles and descriptions to prevent the aforementioned code maintenance issues.