This project was very interesting, because I’d never worked on a project with this many other people. Even in my internship, the projects I worked on included about 10 people total, with about 1 auxiliary team. However in this project, our division had 4 teams, of about 5 people each, and our team leader Hussain did a very good job the first week about meeting with the other leaders thru discord, and setting the design and direction of the teams. Hussain helped us all stay in the loop, talked us through how to run the project, which team was working on which part, and how we could be successful. Week 1 for Atari division was not the strongest, because more was expected of the teams’ preparation for the following implementation week, and the leaders got together and made quick decisions about how to get us back on track so that we weren’t behind. Dan, the division leader, put in a lot of time communicating this week so that we could all catch up and meet expectations/requirements.

For the implementation week, my team became in charge of testing the other teams’ implementation. This was a bit of a struggle because some team’s branches did not have their full commits so when testing the bricks, not all of the bricks were always available. One member of the team would have a different branch than their teams’ branch, for example. Someone our team helped us out by showing us Git Kraken and using the GUI we can see which branch is ahead/behind/working on different parts. This made it a lot easier to pull from various branches and complete our tests. Most of our tests were completed the night before, simply because other teams had completed their methods earlier in the day. Despite working against time, our team still went on a call the night before, and worked out all of our tests. We ran into a few path issues, where sometimes we couldn’t create bricks to test. My VS Code wasn’t compiling and it turned out they weren’t path issues, because after cloning again, it wasn’t recognizing “String”. I had to restart VS Code and troubleshoot with my team to figure this out, and finally they helped me push my tests. We made a new branch to accommodate all the pushing issues we had and our various branches we were pulling from. Our call lasted a couple hours and we had people working on documentation, repo changes, and requirement checking until midnight. Overall, I’m super proud of how well this team comes together to face any challenge, rework when we have to, and deliver the final result. Best team of my academic career thus far because of how well we all get along, communicate, and just show up. It made it easy to learn and get the most out of this class because the team dynamics were to conducive to success.