This is a link to the UPC scanner component that I recently implemented.
This is a link to the Main Layout for the Web App, this is essentially the homepage.
Reflection on What Worked Well
One of the biggest strengths of our team has been our ability to delegate and handle specific tasks effectively. Each team member has taken ownership of different aspects of the project, whether it’s the frontend, backend, or database. This clear division of work has helped ensure that progress is made across all areas of the application. Since I am working on the frontend, I have been able to focus on designing and implementing the UI while relying on my teammates to manage the backend and database.
Reflection on What Didn’t Work Well
Despite our strong ability to divide tasks, one area that has posed challenges is communication. There have been instances where misunderstandings or lack of updates led to delays in task completion. Additionally, not all tasks have been finished in a timely manner, which has put extra pressure on certain aspects of the project. This lack of synchronization has occasionally resulted in blockers, where one team member is waiting on another’s progress to move forward.
Changes to Improve as a Team
To enhance team efficiency, we need to establish better communication channels. This could include:
- Holding short daily stand-up meetings to discuss progress and blockers.
- Setting more reasonable due dates that account for individual workloads and unexpected obstacles. By implementing these changes, we can reduce miscommunication and ensure that tasks are completed within a reasonable timeframe.
Changes to Improve as an Individual
On a personal level, I recognize that I can make improvements by:
- Checking in with my teammates more frequently to see if they need help with their tasks.
- Setting personal deadlines to ensure I complete my work on time.
- Being more open to suggestions and feedback from my team, as collaboration often leads to better solutions. By making these adjustments, I can contribute more effectively to the team and help ensure the overall success of our project.
Apprenticeship Pattern: “Be the Worst”
Summary: This pattern emphasizes surrounding yourself with more skilled individuals so that you can learn and improve at a faster rate. By putting yourself in challenging situations where you are not the most knowledgeable person in the room, you can grow and develop your skills through observation and experience.
Why I Chose This Pattern: During this sprint, I have noticed that I can learn a lot from my teammates, especially in areas I am less experienced in, such as backend development and database management. Rather than just focusing on my own tasks, I want to take the opportunity to learn from their expertise and improve my overall skill set.
How This Pattern Would Have Helped: If I had adopted this mindset earlier in the sprint, I would have been more proactive in asking questions and seeking guidance from my teammates. This could have helped me avoid certain mistakes and speed up my development process. Moving forward, I will embrace this approach to accelerate my learning and become a more well-rounded developer.
From the blog CS@Worcester – Software Dev Capstone by Jaylon Brodie and used with permission of the author. All other rights reserved by the author.