I'm not really going to review the "game" as there is little to review, I'm afraid. What I will do is give some discussion on how to avoid doing this in the future, and I will be touching upon this on Monday's Lecture so ensure that you all attend that.
Coding is a complicated progress that can be quite a lonesome task, and problems can feel impossible from your perspective. But working on it as a team within an environment where you are potentially surrounded by people who have programmed before means that when you do encounter problems there is more than one person whos working on solving the issue. I don't know if you had these problems late in the day as you tried to merge your work or whatever, but some source control would've been massively useful as you can trace back when things go wrong and figure out together what is causing issues.
I would suggest working on creating a foundation of the game within the first couple days of development with moving left and right, collision, placeholder assets, etc. to build up off. So in worst case scenario you have the core to work from. Reflect on what happened, what mistakes were made, and what you are going to do to avoid making the same mistake twice.