Over our second week, we began work on our prototypes and had more discussions with our team about the trajectory of the project — specifically about our expectations as a group: like how we would communicate, and when (and how often) we would hold our meetings.
First of all, we made a sheet of all our collective strengths and weaknesses, as well as our individual work preferences, in order to get an understanding of how it would be best to structure our creative process.
From this, we settled on short weekly meetups on Tuesdays and Fridays, both at 1pm outside of class hours, with our main form of communication otherwise being a dedicated Slack channel. Since this post is being made a few weeks afterwards, I can say that this structure proved to work very well for us and will probably continue to do so for the rest of our project.
For our main task this week, we were assigned with putting together a “team contract” — essentially a rulebook on how we would collectively approach the project:
- Store the project using a shared GitHub
- Maintain a backup of all group files using OneDrive
- Have weekly meetups: Tuesday afternoons (starting at 1pm) & Friday afternoons before games business class (also starting 1pm)
- Use Slack for online communication: one channel for posting/sharing our work and another for casual group talk
- Don’t rule out any conflicting ideas. Experiment and ideate, but still keep time constraints in mind!
- Set weekly deadlines and objectives to keep us motivated and working consistently
- What motivates us:
- sense of achievement
- fulfilling the game vision
- creating a great player experience
I think this was a good team-building activity to get a stronger consensus for how we approach development, strengthening our communication as a team.
–
I also made significant progress on my game development this week, including a functioning prototype that would act as a groundwork for the future of my role in the project.
For a more detailed overview, check this page.
Leave a Reply