We began our class with a rather lengthy scum meeting, since there was a lot of stuff to cover – we needed to sort out what the given roles would mean within the project and how we would handle our pre-production. We’ve given ourselves a lofty production schedule, where we’re aiming to finish our MVP in half the time, while focusing on our stretch goals for the other half. I think it’s so important for everyone working on this project that they appreciate that there is a high expectation and we’re looking for an excellent, quality product at the end of the deadline.
With that said, we covered all the needs for pre-production, based on the information we’ve been given by the lecturers. I think the first thing we always look to is setting up the project management, so it’s out of the way and we have no excuses in terms of communication, back-ups, and so on.
Luckily, since this was our pitch, Marc and I already had some of this information on hand. I set up a shared drive through Google, since I bought a storage expansion for our last project and may as well use it for this. Trello was something the lecturers wanted a bit more control over this time, so Gary and Rachel actually set up the board for us; we followed Gary’s advice on how to organise the cards this time, which differed from how we organised our board last time.
The cards we’ve got to work with are:
- Team Members: there’s one card for each member, where we can store things like our individual production schedules or our contribution forms.
- Scrum Minutes: very important!
- Research and References: we’ve got all the assets listed and people can put in any of images they want to reference while concepting or modelling.
- Pre-Production Documentation: we’ve got to-do lists, schedules, the audio plan, and other documentation that we can reference throughout development.
- 2D Tasks (To-Do), 2D Tasks (In Progress), and 2D Tasks (To Review)
- 3D Tasks (To-Do), 3D Tasks (In Progress), and 3D Tasks (To Review)
- In-Engine Tasks (To-Do), In-Engine Tasks (In Progress), In-Engine Tasks (To Review), and In-Engine DONE
We’ll move the asset cards around depending on what state they’re in, but this set-up also allows us to move cards back in the pipeline if things need to be revisited at any point along the way. We’ll also be using the labels for priorities (high, medium, low) and we’ll assign team members to the cards so everyone knows who is working on any particular asset.
Everyone seems to know what they’re working on – the modellers have chosen a hero piece each that they will follow through the entire pipeline while the concept artists start coming up with ideas for the other remaining assets. I’m pouring my focus into the documentation side of things, working through as many project management tasks quickly so I can return focus on building/programming.