Collection: Team Project 2 | Individual-CA

TP2 | Mentoring

Mentoring Overview

For this semester I volunteered to take part in the 3rd year mentoring programme. The reason for this was that without the help of mentors last year I probably would not have been able to complete anything resembling a game, and I wanted the opportunity to help the new 3rd years similarly. My specialization was sound, physics and process, however considering I dabbled in every aspect of XNA last year I felt I would be able to help my group with almost all problems. I was paired with Cormac Matthews in helping Pioneer Games, I was both blessed and cursed that the group seem to be one of the best in the year and had fairly few issues throughout the year, leading me to mainly help with scope and user testing and pointing out useful tutorials. I also throughout the course of the mentoring helped out with troubleshooting problems for other mention such as Ronan's groups camera issues. 

I feel that I lent as much time as much time as was possible and required, however my group exceeded my expectations so therefore taking on board what I did for them and the small bits of help for other groups I feel in the scale of small / medium / large portions of time I spent a medium amount of my individual time with the groups.

TP2 | Mentoring RSS

 

Meeting 4 - 4th April

Product:

  • Xact Setup Instruction
  • Scope Advice
  • Planning for Alpha

Process:

This week the group filled me in on how their Proof of Concept went and the feed back that they got as a result. We went through their plan for the work they had left to do and I gave them some advice on defining the scope for their final release. They explained some of the issues they had with regards to getting collision code and indicated that this would be a thing they would need help with in the future.

James indicated that he would be getting the sound manager code from Niall soon so I went through the tutorials how to set up an Xact sound library and separate sounds into categories with him so he would be able to have his library set up and ready for when he received the code. 

Issue:

Meeting 3 - 15th March

Product:

  • Development Update
  • Presentation Prep
  • Process Tips

Process:

This weeks meeting was very straight forward as the group seem to be moving forward at a great pace and don't seem to be running into any difficulties with regards to my areas of expertise. The main thing I helped them with was their presentation preparation as they were getting ready to present their proof of concept presentation. I gave them a few pointers on what they should be including in their presentation.

I also this week relayed some advice that we had been given on the scrum process as well as watching a run through of their game. I spotted a few issues with object placement in the game where objects were not touching the ground or they could be placed better.

Issue:

Meeting 2 - 1st March

Product:

  • Cross Group Help
  • Group Access

Process:

This week my group fell victim to RAG week and were not around on tuesday to meet at the regular time. For this reason I went with Ronan to his group meeting to see if there was anything in his group that I could help out with. His group is called Team Cyberdyne and they have made some good progress. They had a problem with their first person camera luckily it was a problem that we had both seen before so we were able to point them in the right direction. 

I also this week got access to my own groups mahara group so that I can track their progress through that.

Issue:

Meeting 1 - 23rd February

Product:

  • First Group Meeting
  • Introductions
  • Group Access
  • Game Breakdown
  • Group Role Familiarity

Process:

 This week was the first week of the mentoring programme I volunteered for with the 3rd year Games group. I got matched up with Cormac Matthews in mentoring Pioneer Games. This group consists of Nicholas Grassick(Programmer), James Gilsenan (Sound Design), Georgijs Sidorovs (Modelling) and Kenneth Clifford(Scrum Master). We met with them on Tuesday to get a brief overview of their game, their roles and how they had gotten on with their paper prototype. 

After we had gotten up to speed on their game idea we started to ask about certain aspects of their game and their roles. The game is a isometric puzzle game twinned with a roman style battle arena. The game would use 2 cameras a normal one for when fighting in the arena and an isometric one for the puzzle section in the game which would involve the finding and placing of cogs to open a bridge to the next section. 

Cormac spent some time talking to Georgijs about 3D modelling and while he was doing this I spoke to James about Sound Implementation and Nicholas about some of the game features that they wanted to implement. I told them to be careful about their scope and what they would be able to get done in the short time-frame that they have. They seem to understand that it is important to drop some features if it proves too difficult or time consuming for the good of the game as a whole. I also gave them some pointers on scrumwise and how to plan ahead.

Issue:

Details

Text