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

Sprint 1

What went well

  • Good adaptation to the new techstack;
  • What was done is well implemented;
  • Intrateam communication;

What to Improve (and Verifiable action points for Sprint 2)

  • Communication with other teams;

there will be more open communication with other teams during development. There should be no confusion about overall project direction and status, we should be more comfortable asking questions.

  • Knowledge about the deployment pipeline;

research about the topic

  • Feature development effort estimation;

in-depth analysis of the features prior to the attribution of the estimate

  • Be more clear on responsibility distribution inside the team (Try to define roles and workload, more concrete sprint planning);

there will be better and more balanced work distribution within the team. Each member should have a specific assigned task. Try to define roles and workload, more concrete sprint planning

Sprint 2

What went well

  • Intrateam communication, especially with the product owner and during sprint planning;
  • Estimation of effort associated with feature development was more accurate;
  • We gathered a lot of knowledge about the deployment pipeline and overall project integration ideas, which was lacking;
  • The deployment pipeline was implemented without major problems;

What to Improve (and Verifiable action points for Sprint 3)

  • Communication with other teams;

Communication with the groups in the TP class was smooth due to the weekly lectures, but communication with the teams outside the TP can always be improved, namely with questions about integration of features. We must be less shy when in need of answering our own doubts.

  • Workload distribution within the team can be better balanced;

We will forcefully assign each team member at least one specific task on sprint planning to avoid idling as much as possible