This content originally appeared on DEV Community and was authored by Aqeel Akbari
In our third and final project, we were split up into division called the ATARI-DIVISION. We worked in a much larger team and our task was to find all the bugs and fix them in an already implemented game of Tetris.
Overall:
Despite there being a lot more work to go around in this project, it was actually not nearly as stressful or time consuming as the previous projects. This was definitely in part because I was not in any of the leadership positions, but it was also because of the amount of people that we had.
Week 1:
During week one each team was assigned a package or two in the project and was tasked with understanding and finding bugs. We also built up our communication, specifically we used a discord server. I found many bugs inside of the events package and came to understand the code quite a bit. After drafting up a document of what needed to be fixed or changed, most of the work for our group was done. We also had to make a design document but the entire division was working together to do this. The only other thing that needed to be achieved was the team documentation and staying up to date with the rest of the division. Week 1 went very smooth and it was a lot of fun to understand the implementation of the given code.
Week 2:
During week two is when we went about fixing things and adding our own touch. Overall the bug fixing went really well, I think the work was spread out decently and the tasks got done in a timely manner. We also had to update the design document with the new methods that we thought of in this part. I updated the design doc and reviewed code in the part of the project.
Communication:
We used discord to communicate. It was very successful. There was private channels for each team as well as a division channel. This allowed us to contact our team for our divided up tasks but also communicate between all the other teams when needed. This way worked a lot better than having a couple communicators that had all the info. We also had communicators but their role was not as important this time around. We also had big division wide meetings were anyone was allowed to join. These were very helpful to get a grasp of what needed to be done and what had already gotten done.
To conclude, this project went very well. Tasks were divided well and communication was good. I also had a lot of fun doing certain portions.
This content originally appeared on DEV Community and was authored by Aqeel Akbari
Aqeel Akbari | Sciencx (2024-11-06T22:09:54+00:00) Project 3 – Tetris Game. Retrieved from https://www.scien.cx/2024/11/06/project-3-tetris-game/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.