App

Improvement Cycle – http://goo.gl/4adBWe


Hard Skills, Soft Skills and Processes

During this project, I have learned a few new skills and processes and improved on a lot of others.

KPI meetings

This is the first time I have filled out a KPI form and done a KPI meeting before, the experience was amazing! Thoroughly enjoyed it and it was so worth while. I haven’t decided yet if I should continue to do long KPI responses in the KPI form or not yet, maybe I will cut it down, possibly up to 50%? I will see when the next one comes around.

Pitches

I think I am sslloowwllyy getting better at doing pitches, I have looked back at my pitch presentations and although I still have my script in front of me, and that I may stuff up a little, that little bit is getting littler every time. Next time is the new project pitch, so between now and then, I will have a totally new game idea that will hopefully make me more excited about the idea, so I aim to do even better!

Collaborating

This is the first time we have worked with SAE students outside of our classes, and even in different disciplines. We worked with Animation students through the process of model design and ended up with two fully sick 3D Gladiator models. They look very tough and their chests look very out of proportion with the rest of their bodies, which is exactly what we want. The Animation students, especially Brennan, were very active and very helpful, seeming very enthused about our project, even delaying their whole class by half an hour, just to play our finished product. What sweethearts! I am glad that they did get to play the finished product, as even though they haven’t been in the games design part of the journey, they have been there by our sides nearly the whole way through, and have supported us and have given us two models which they deserve to play a game worth.

Repositories

By now, we have used Repo’s so often that you would think we know the bulk of things. Well until this project, I didn’t realise there was a ‘Commit’ button. Every time there was a version someone else had pushed to the repo I handled and I tried pushing afterwards, there would be a merging error. Previously I knew to always pull before I pushed, but sometimes you forget these things and you would end up with a repo that didn’t want to pull because there was already a push request waiting to be sent, and it didn’t want to push because there was a pull that was available. At the point you would have to delete your version of the repo or create a new one and put all files in, but I discovered that pushing the ‘Commit’ button somehow merges these two elements together, it somehow pushes and pulls without complaining and keeps everything from both editions unless there are conflict errors which are really easy to solve. I also learnt how to make a pull request, instead of forking your own version. That was fun I guess, a new experience for me anyway.

Brainstorming Ideas

From a Games Designer point of view, I am a terrible brainstormer, but through the integration of ideas from the facilitators, I now understand what a good game may look like and all the elements and ideas that make a game good. Our game would surely not be the same without the idea injections from Tony and Steve nearly every lesson. Near the end of the project, I was getting really good at brainstorming fixes for problems that were pointed out in play sessions, and could explain my point much better than previously. Previously it was a lot of drawing out what I saw in my head, now I know more terminology and can explain my point with my extended game development vocabulary.

Pivoting

Receiving feedback from the many playtests has been amazing. A lot of our game ideas, mechanics and dynamics have come from the feedback we have received from the playtests. Grabbing these ideas and turning them into a better product has been a process which I have become better at and enjoyed. Instead of just writing notes down of ideas I have from what the feedback has given me, I now keep a record of what was actually said as the feedback, to look at before future playtest sessions.

I believe that this feedback will also be useful in future projects as all humans are not perfect, we can not remember everything and anything, I can’t even remember what I had for breakfast this morning. Having the actual feedback written down or saved somewhere is a great plan for future projects to look back on, if you remember there being a problem that you solved from feedback in a previous project, if not, looking back at previous feedback shows that you have improved, which is always a bonus when learning.


This is Daniel Jochem, signing out.

Advertisements