During this sprint, we faced a significant challenge when one of our teammates dropped the class a few days before the due date without notifying the group. This unexpected development impacted our ability to complete the frontend portion of the project as planned. Despite this setback, we made substantial progress on the backend, meeting many of our goals thanks to increased collaboration and frequent meetings.

This sprint we had a much better communication process, our team adapted by meeting more frequently and ensuring everyone was on the same page. We delivered the backend changes on time and made efforts to divide tasks more effectively. However, due to the sudden loss of a team member, we were unable to fully implement the frontend features that relied on their contributions.

Moving forward, an important factor will be proactive and transparent communication. We’ve learned that consistent updates and check-ins are essential to reduce the impact of unforeseen events like our teammate dropping. For future sprints, we will continue to prioritize collaboration and ensure task dependencies are minimized by distributing responsibilities more evenly across the team.

Although we couldn’t complete the frontend work, the backend development was successful, and we’re confident that the lessons learned will help us move forward with a more robust process.