When Teamwork Works

This week, I spent a large portion of my time working on our group project with my team. I am especially glad that we were approved to work as a group of five because it allowed our whole group to stay together and contribute to the same project. My main focus was building the first working skeleton of my assigned slice, including the data layer, tests, and JavaFX scenes. I also spent time connecting my work to the shared parts of the project, which helped me better understand how individual features depend on the structure created by the rest of the team. A major part of the week involved collaboration and integration rather than only writing my own code. Several of us needed to work with the same shared files, so we had to communicate about changes, resolve conflicts carefully, and make sure one person’s work did not break another person’s slice. We have also been meeting outside of our originally planned meeting times whenever necessary so that everyone stays on the same page. Pulling teammates’ branches, running their code, reviewing pull requests, and testing how our pieces worked together showed me how important communication is in a group coding project. Working with this team has honestly been a breath of fresh air compared with some of the other team coding projects I have experienced. Everyone has been willing to communicate, help each other troubleshoot problems, and adjust plans when integration issues come up. This week made the project feel much more like real collaborative software development because we were balancing individual responsibilities with shared decisions and team-wide testing. I am proud of the progress we have made so far, and I am excited to see how our application turns out as all five slices continue coming together.