Sprint Retrospectives 7.2 - FEUP-MEIC-DS-2025-26/madeinportugal.store GitHub Wiki
Sprint 1 Retrospective
What Went Well
- Code reviews showed clear improvement compared to Sprint 0.
- The Pub/Sub system was successfully implemented and integrated.
- Image validation was completed, resolving previous related issues.
- Other prototypes integrated smoothly with our Pub/Sub system.
- Communication with other teams was productive, including coordination outside our class.
What Went Wrong
- Some planned tasks were not completed, such as improving the search distance metric and enhancing search relevance.
- Team communication was strong in the first week but declined later due to overlapping deadlines from other courses.
- There was noticeable reliance on certain team members, which created bottlenecks when they were unavailable.
What Is Still a Problem
- A few technical improvements, particularly related to search relevance and system refinement, remain incomplete.
- Some integration-related issues and enhancements were postponed and still require attention.
- The workload distribution problem persists, with uneven task ownership continuing to pose a risk for future sprints.
Sprint 2 Retrospective
What Went Well
- Productivity increased significantly compared to Sprint 1, with all initially planned issues being successfully completed.
- Communication improved, both within the team and with other prototype groups, enabling smoother integration and faster resolution of doubts.
- The team handled external academic pressures better than in the previous sprint, reducing the impact of conflicting deadlines on progress.
- Workload distribution became more balanced, lowering dependency on specific members and improving collective ownership of tasks.
What Went Wrong
- External course deadlines and dependencies still caused some minor delays, despite better mitigation.
- A few tasks required additional refinement after completion due to evolving requirements.
What Is Still a Problem
- Overlapping deliverables from other courses can still disrupt planning and focus.
- Some areas of the system, particularly search relevance improvements, still require further refinement in future sprints.