This week, we continued working on our team management, specifically team contract and user stories.

Team contract is something that ensures no boundaries are crossed and no rules are broken while developing the game. It was written down after a discussion with everyone on the team and I shared it on Slack .

Work preferences are also really important when it comes to teamwork, so everyone present that day had an opportunity to share their strength and struggles with everyone else. it helped us understand what everyone’s work pattern is to ensure the project runs smoothly.

My work preferences aren’t very aligning with team work, but my flexibility and ability to communicate at any time of the day should make up for it. Everyone on the team has a problem with deadlines, but I think by regulating each other and keeping track of things together it shouldn’t be ass troublesome.

After the team contract and work preferences have been established, we moved on to finally mapping out our tasks for the project with user stories.

User stories are short statements from the point of view of the customer/player that puts their wishes into words. It helps the team figure out where they will be working together and which part of the game require group effort.

I’ve put in first three user stories on the board as other people struggled to understand what they were for, so I took the initiative of explaining and providing examples for others.

User stories ended up ding very narrative heavy, as was expected from a game where mechanics are simple and don’t take up much of game’s content.

The tasks everyone came up with are connected to each user story and intertwine with each other. The first task I have started was a narrative flow chart (apart from researching the GDD). Because it plays such a big role in the game, everyone was kind of relying on me to finish it by the end of week 3 to have a basic understanding of what we need to do.