This week was presenting our first milestone in front of Brian. We had organised plenty of team meeting to make sure we had a good understanding of what we wanted to say for the presentation.
Despite the fact I had to read from my notes frequently, the content of the presentation seemed to be enough to help us get a good grade. This was good news for the team as the grade for the last task wasn't very good making us unsure about our project. Getting this grade really motivated the team as we now know that with the last task the content was good, it just wasn't organised and presented good enough for anyone to really understand our project.
This next few weeks will be focused on creating a Design Document now. This has been noted quite a few times over the last few updates, but with the first milestone complete the focus will be on getting this completed now. With the team not getting a good grade from the first task, a lot of focus was put on this presentation to make sure we got back on track towards getting a good grade from this project.
Tuesday, 30 November 2010
Sunday, 21 November 2010
First Milestone Week 8
This week we had a dry run of our first milestone presentation. It went well, though the information was quite a lot to take in. The advice was to add more visual aids to the presentation.
Work on our design document has been slow once again. This will pick up once we have done our presentation on Thursday (November 25th). The work towards it has been a loss of focus as the work seem to look more like notes for our final report than a design document.
This week work of the design document is the main focus. Discussions on the software to create our levels in is also needed for this week.
Work on our design document has been slow once again. This will pick up once we have done our presentation on Thursday (November 25th). The work towards it has been a loss of focus as the work seem to look more like notes for our final report than a design document.
This week work of the design document is the main focus. Discussions on the software to create our levels in is also needed for this week.
Sunday, 14 November 2010
First Milestone Week 7
This week has been focused on making sure we get our done for the first milestone presentation during Week 9 of the overall assignment.
There are have been lots of meetings to make sure we have everything we need for this presentation because will will be having a Practice Presentation on Wednesday (17th November 2010).
There has been work towards our Design Document too this week, however progress on that has been slow due to our focus towards our first milestone presentation.
Greater understanding on how to create a worthwhile test for the project took a big step in the right direction this week with the idea of misleading players by playing with their understand of previous knowledge and life experiences.
An example one of our team members wrote up was this:
"For example, applying this style of misdirection to an object in game a player is asked to find the “missing key” to progress to the next room. In their current room there are many objects the player can interact with ranging from a table lamp to a statue. The door is what the player would most associate a key to be related to; however the key they should be looking for would be a key from a piano."
This kind of play on words seems to to be a good direction for our overall test. Nothing is final at this stage, but research into this idea is going to done to see how we can make a worthwhile test to help find important data to help improve game design overall.
There are have been lots of meetings to make sure we have everything we need for this presentation because will will be having a Practice Presentation on Wednesday (17th November 2010).
There has been work towards our Design Document too this week, however progress on that has been slow due to our focus towards our first milestone presentation.
Greater understanding on how to create a worthwhile test for the project took a big step in the right direction this week with the idea of misleading players by playing with their understand of previous knowledge and life experiences.
An example one of our team members wrote up was this:
"For example, applying this style of misdirection to an object in game a player is asked to find the “missing key” to progress to the next room. In their current room there are many objects the player can interact with ranging from a table lamp to a statue. The door is what the player would most associate a key to be related to; however the key they should be looking for would be a key from a piano."
This kind of play on words seems to to be a good direction for our overall test. Nothing is final at this stage, but research into this idea is going to done to see how we can make a worthwhile test to help find important data to help improve game design overall.
Sunday, 7 November 2010
Literature Review Presentation Week 6
This week was just a case of presenting our literature review to the lecturers. The team organized the structure of the presentation and had a few practice sessions before giving the presentation itself.
The lecturers see to this we had good content, though feedback was rather minimal. Case study into Video Games with Misdirection and only allowing one person to present instead of four were the key points taken from the lecturers.
This weeks focus is into finding games with misdirection, if possible, to help with out project. Also work towards our First Milestone, which is to create a design document, is need for this week.
The lecturers see to this we had good content, though feedback was rather minimal. Case study into Video Games with Misdirection and only allowing one person to present instead of four were the key points taken from the lecturers.
This weeks focus is into finding games with misdirection, if possible, to help with out project. Also work towards our First Milestone, which is to create a design document, is need for this week.
Subscribe to:
Posts (Atom)