This will be the first 4 weeks of our meetings complied into one, as well as reflections and how well we are working as a team.
Week 1 Meeting (31/1/25)
By the first week, we had begun to finalise our roles in terms of who is doing what in our group. The final lineup consists of:
- Sam as our Technical Designer. Tasks include: Programming and UI/UX.
- Esi as our Character Artist. Tasks include: Character Art and 3D Modelling.
- Camilla as our Mechanics Designer. Tasks include: Mechanic Ideation and Prototyping.
- Guy as our World Designer. Tasks include: Environment Ideation and Implementation.
- Carter as our Environmental Artist. Tasks include: Object asset making and implementation.
Esi and Carter did a swap as they were both more comfortable with each others tasks. We have also made a discord to ensure that everyone gets the latest updates and news about tasks.
On Friday, everyone met up and discussed what their role would entail and here were the first set of tasks (overall):
| Esi | Camilla | Carter | Sam | Guy |
| – Research artstyle – Create 3D models for ETA + first God (Gravity) – Sketch Superflat / 00s Vectors – Simple animation (God Floating) | – Blocking out level – Sketching out level (inc. portals/checkpoints) – Build the level – Partly QA – Narrative though design | – Sketch out modes for environment – Create models – Create 10 interactable objects (tables, lamp etc) | – Make gravity mechanic (power up) – Provisional (UI + Main menu) Assist mode (accessibility option) | – Code movement + rotation – Code jumping + Character rolling inside of ball movement |
What we actually needed to do in the week was:
- Sam to start programming the basic build.
- Esi to start drawing the turnaround for the character.
- Camilla to start looking at the mechanics and how they can be implemented.
- Guy to start sketching the worlds and how everything would be formatted.
- Carter to start noting what assets he needs to make and make them.
Communication this week: ⭐⭐⭐
We made a discord immediately and communicate what we needed to do that week, however, not everyone could make it into the meeting so there was less of a shared understanding.
Teamwork this week: ⭐⭐⭐⭐
As we sorted out our tasks, we evened out tasks based on how much work someone is taking compared to another. Sam was taking on lots of coding, so the others offered to help him with other aspects of the build such as the UI.
Organisation this week: ⭐⭐⭐
We had a slow start this week, but our discord allows us to contact each other in a remote way, meaning those who were sick could keep in touch with the rest of the team.
Week 2 Meeting (7/2/25)
The week 2 meeting only had Esi and Sam involved, as Camilla was sick, Guy was away and Carter could not make it, so we just discussed how our tasks were going.
Sam was implementing more features into the build, he added camera rotation and objects to move and knock over. Esi gave him some feedback on the discord about what could be implemented.
Esi continued drawing the turnaround for the main character, Eta.
Carter said that he would continue working on his assets.
Guy was away, but he still worked on sketching some of the world designs.
Lastly, since Camilla was sick, mechanics has gone to Sam, but Camilla is fine with programming the UI. She worked on coding.
Communication this week: ⭐⭐⭐
A few people were away and sick, but we made a Jira to delegate tasks and everyone has been adding onto it. Communcation overall has been rocky with people sick and/or away however.
Teamwork this week: ⭐⭐
We haven’t been coming together as a group a lot this week outside of classes, and this week has only been Carter, Esi and Sam, so the teamwork wasn’t very strong this week.
Organisation this week: ⭐⭐
This week was a bit all over the place, but it was mainly due to the absences of the members. Everyone was still doing their tasks in their free time.
Week 3 Meeting (14/2/25)
This week, the meeting was decided to be on the 14th, but Esi, Carter and Guy could not make it, so Sam and Camilla discussed how their tasks fared for that week.
The group made an instagram page of the game, so that people could hear more about it.
The tasks for this week were:
- Sam to continue programming the basic build.
- Esi to start creating the 3D model for Eta.
- Camilla to learning to code for the mechanics.
- Guy to finish sketching the world and finalise the design.
- Carter to finish assets and implement into unity.
Communication this week: ⭐⭐
Meeting happened very impromptu, meaning people missed it. There wasn’t much talk in the Discord this week other than a few progress screenshot sharing.
Teamwork this week: ⭐⭐
We haven’t been doing much group problem solving this week and have been working individually.
Organisation this week: ⭐⭐
We don’t have many set groups as a group, so that has weakened our organisation.
Week 4 Meeting (21/2/25)
The groups work this week has slowly been coming together.
- Carter has been implementing the toon shader into unity as well as importing all his assets into the hub world
- Sam adding a timer to the build and working on the build
- Camilla continuing to learn code for the UI
- Guy creating a test world in Unity
- Esi finishing the 1st 3D model for Eta.
This week has been pretty quiet overall, and no meeting this week. Next week is the playtest so hopefully the group starts to meet more.
Communication this week: ⭐⭐
Not as strong as the first week, but we have been trying to inform each other more about what we have done.
Teamwork this week: ⭐⭐⭐
We’ve been talking more on the discord about our task progress.
Organisation this week: ⭐
Not very strong. The Jira hasn’t been updated and we’ve moved back to discord for sharing updates.
Reflection?
The first four weeks of our groups meetings have been a bit rocky, but when we do meet, everyone has a goal they need to finish in that week. If we just communicate more what we can and can’t do, I think our team could be really strong.