This is the link showing merged changes into main branch after testing. During this sprint, our team collaboration was strong, with regular meetings during class checking on our progress and open communication that helped us stay aligned. Additionally, our task management system in GitLab was highly effective, helping us track progress and ensure that every team member had a clear understanding of their responsibilities. Another success was our ability to quickly adapt to challenges. When any of my teammates encountered any problems, we worked together to identify solutions and implement fixes efficiently. This adaptability was important in maintaining our project’s momentum and meeting our sprint goals. Despite the successes, there were areas where I struggled. One significant challenge was time. Some tasks took longer than anticipated due to unforeseen problems, particularly when dealing with the display of the First Entry Date in the frontend. I made some changes in the GuestInfoComponent.vue and at first it wasn’t displaying the entry date. With more research, I figured I also had to make changes in the VerifyPage.vue file. With these changes, my Date of first Entry was displayed after making my changes. Looking ahead, there are several ways our team can improve. One is better estimation of task complexity, where tasks can be broken down further and allocate time for unexpected challenges. Reflecting on my own contributions, there are several areas where I can improve. One is time management. Allocating more time for testing will help ensure deadlines are met more comfortably. This I would say is something I am going to do better at in the next sprint, as I believe it will help enhance my own skills as a developer.
The Apprenticeship Pattern I chose is “Expose your Ignorance” pattern which encourages developers to openly acknowledge what they don’t know and actively seek knowledge. Instead of pretending to understand everything, developers should ask questions, collaborate with teammates, and use resources to expand their expertise. I chose this pattern because it closely aligns with my experience during this sprint. When working on merging my work to GitLab after I had completed my issue, I struggled with this and came across many blocks. Instead of immediately asking for guidance, I spent too much time doing it on my own. Eventually, when I reached out to a teammate, I realized how quickly I could have resolved the issue with just a simple discussion. This experience reinforced the importance of embracing learning opportunities rather than trying to figure everything out alone. Had I fully embraced this pattern from the beginning, I would have immediately sought help. This approach would have saved me valuable time and reduced frustration. Moving forward, I plan to be more open about my knowledge gaps, actively seek advice, and continue improving my problem-solving efficiency. This sprint was a valuable learning experience that highlighted both our team’s strengths and areas for improvement. While our collaboration and adaptability were commendable, we also identified opportunities to enhance efficiency and communication. On a personal level, recognizing the importance of seeking knowledge earlier will help me grow as a developer. By implementing these improvements, both individually and as a team, we can ensure even greater success in future sprints. I look forward to working on the next sprint and implementing more changes that will make this sprint easier.
From the blog CS@Worcester – Lynn'sBlogs by lynnnsubuga and used with permission of the author. All other rights reserved by the author.