During Sprint 2, our team focused on improving both our workflow and communication while continuing to develop our project. Compared to Sprint 1, this sprint felt more organized, and we were able to complete all assigned tasks on time. This retrospective reflects on what went well, what could be improved, and how I can grow both as a team member and as an individual.
What Worked Well
What worked well during this sprint is that everyone completed their assigned tasks on time. Compared to the first sprint, our communication improved significantly. We were more consistent with updates and clearer about responsibilities, which helped avoid confusion. Even when we had to work remotely or adjust schedules, the team stayed accountable and ensured that all deliverables were completed. Additionally, we received good feedback from the professor, which confirmed that we are moving in the right direction.
What Didn’t Work Well
One of the main challenges during this sprint was coordinating schedules. Since everyone had different availability, we had to rely more on remote meetings, which were not always as efficient as meeting in person. While we were still able to complete everything on time, communication could sometimes feel delayed. However, despite these challenges, the team remained responsible, and everyone fulfilled their role, which ultimately allowed the sprint to succeed.
Improvements as a Team
To improve as a team, we could focus on better scheduling and planning meetings in advance. Setting a fixed weekly meeting time could help ensure that everyone is available and reduce the need for last-minute coordination. Additionally, using clearer communication tools or setting expectations for response times could help us stay even more aligned. Improving documentation of our work could also make it easier to track progress and support collaboration.
Improvements as an Individual
As an individual, I can improve by being more proactive in communication. Even though I completed my tasks on time, I could provide more frequent updates to keep the team informed. I can also work on better time management to avoid any last-minute pressure and contribute more actively during team discussions. Being more engaged in planning and helping others when possible would also strengthen my role within the team.
Apprenticeship Pattern: “Breakable Toys”
The pattern I selected is “Breakable Toys” from the Apprenticeship Patterns book. This pattern encourages developers to build small, experimental projects where they can freely explore ideas, make mistakes, and learn without fear of failure.
This pattern is relevant to my experience during the sprint because there were moments when I hesitated to try new approaches, especially when working on features that affected the main project. I focused more on completing tasks correctly rather than experimenting or exploring alternative solutions. If I had applied this pattern, I might have created smaller test versions of my work to better understand different approaches before implementing them in the main project.
Having read this pattern earlier, I would have been more confident in experimenting and learning through trial and error. Instead of worrying about making mistakes, I would have used them as opportunities to improve my understanding. This approach could have helped me develop stronger problem-solving skills and contribute more innovative ideas to the team.
Final Thoughts
Overall, Sprint 2 was a success. We improved our communication, completed all tasks on time, and received positive feedback. While there are still areas to improve, especially in scheduling and communication, the team is progressing well. I look forward to applying these lessons in the next sprint and continuing to grow both technically and professionally.
GitLab Link #1 : I implemented my assigned feature and pushed the completed code to the repository, updated the issue tracker with progress and marked tasks as completed once finished.
Maria Delia 