Sprint 1

• What Went Well

  • Team organization and work division Tasks were divided clearly among team members, which helped avoid overlaps, reduced blockers, and made it easier for everyone to focus on their responsibilities and deliver on time.

  • Exploring different implementations The team experimented with multiple technical approaches before deciding on the final solution, which improved understanding of the problem space and increased confidence in the chosen implementation.

  • Communication with team members Day‑to‑day communication between team members worked smoothly, with people being responsive on chat and in meetings, which helped resolve doubts quickly and kept work aligned.

• What could be improved

  • Communication with other teams Alignment with other teams was sometimes late or unclear, which caused delays and rework; next sprint, more proactive syncs and earlier clarification of dependencies are needed.

  • Meet more times with team members While communication was good, the team could benefit from more frequent short check‑ins to surface issues earlier and adjust priorities before the end of the sprint.

Sprint 2

• What Went Well

  • Improved collaboration with other teams Communication with the platform and infrastructure teams was smoother compared to Sprint 1, which helped align expectations and clarify integration points.

  • GitHub Actions and automation progress Advanced the CI/CD process, improving the reliability of deployments and reducing manual steps.

  • Stable pub/sub workflow Internal pub/sub mechanisms and asynchronous communication tools worked reliably throughout the sprint, making deployments, logs and coordination smoother.

  • Independent microfrontend integration Success in deploying the microfrontend independently on MadeInPortugal.store

• What could be improved

  • Coordination for Product Page integration Although the microfrontend is deployed on the platform, lack of synchronised timing with the Product Page prevented the component from being mounted on the actual page during the sprint.

  • Product data consistency Inconsistent handling of the shared product catalog caused unexpected issues in our microfrontend when products were removed or replaced without a clear standard. Defining a simple product-creation standard would help avoid similar problems in future sprints.