Pre-Production Learning Reflection


Welcome to a new devlog! This will be more of a re-cap or postmortem of what my team and I have accomplished in around 3 months of work, and how this work will help us in the future.

Documentation

We're in that first stage of the development cycle, pre-production, and it's incredibly important that in this stage we understand what our game truly is. My team and I have created documents such as our GDD, risk tables, schedule plans, project plans, and a team charter which has helped us spark communication about what this project means to us, how each of us is involved in the project, and actionable schedules we can follow for the future moths of development. In terms of practicality, I believe half of these documents will never be looked at again such as the risk document and the team charter, however, these documents replicate the desires of any publishers or stakeholder so going through the process now is essential to grasp the concept of these documents. 

Proof Of Concept

While some of our team focused on documentation, me and another member started developing our mechanics in engine for a proof of concept! We hope to build all of the base features so that sometime in the next few months we will have tools readily available for the designers to use and create content in-engine. Our game is programming-heavy with the many mechanics we've decided to include, so getting an early start to the proof of concept will help us hasten our development time going forward.

Comments

Log in with itch.io to leave a comment.

Using your proof of concept as sort of a launching point for the whole game seems smart given how much programming is required. Even if you end up throwing it out, it should still give you a decent understanding of how to implement your mechanics much quicker.

Hi Lucas, I totally get what you're saying when it comes to the some of the documents probably not getting much use going forward, but as you've said the ideas and concepts behind them spark important talks for our teams to have. In actuality who knows if they'll come of use or not, but it's always good to have something to fall back on if things fall apart.