Sprint Retrospectives 5.1 - FEUP-MEIC-DS-2025-26/madeinportugal.store GitHub Wiki

Sprint 1

Positive points

  • Good expertise by the whole team of the technologies used;
  • Good velocity on the resolution of problems;
  • A quick meeting on Saturday before the end of the sprint proves being useful to replan sprints and update everyone on the status of the work.

Process suggestions and improvements

  • More focus on the team deliverables, instead of the project needs as a whole (within reason);
  • More focus on new features, instead of perfecting existing ones (within reason).

Blockers

  • Communication with other teams has been really inefficient and the source of a lot of bottlenecks, especially with integration tasks;
  • The missing production architecture does not allow us to deploy with confidence the features integrated with the entire product;
  • The missing delegation of tasks outside the singular teams makes important tasks (like the definition and deployment of the production architecture) impossible to be done;
  • The needed work outside the user stories of our team meant that this sprint required too much effort for us, while not delivering as we expected.

Sprint 2

Positive points

  • Most of the promised tasks for this sprint were done without impediments or mocks;
  • The integration with the production infrastructure is done, even after a lot of problems.

Process suggestions and improvements

  • Make more decisions for the teams and communicate with them as quickly as possible to Teams.

Blockers

  • Scrum Master was sick during the weekend;
  • Being one of the first groups that integrated with the production infrastructure meant that we faced more issues by ourselves;
  • Asynchronous communication between teams is really inefficient via Teams;
  • Infrastructure-related components were not ready in time to be fully integrated (e.g., authentication).

Sprint 3

// TODO