2012/2013, 2nd quarter, timeslot D (Wed 13-19, Fri 09-17)
INFOB1PGT: Gametechnologie introductieproject
Coordination: Arno Kamphuis (WWW, Email)
news | schedule | resources | teams | description | opdracht | vereisten | beoordeling | symposium | contact
Every team member is individually responsible for the success of the project. The team and each of its members have to make sure that the deliverables (cf. below) are finished and submitted in time. Each team member should contribute equally to the project. Since this course is credited with 7.5 ECTS, this means about 200 working hours per person (1 ECTS relates to 25-30h). In order to verify your contributions (both time and quality wise), each member is supposed to keep a logbook. This should at least contain the working hours you put in each day, a short description on what you have done, and it should be updated at least once a week (preferably the day before the meeting with the tutor, so he can check your progress before the meeting). The form of the logbook has to be dicussed with the tutor who has to make the final decision about it. A good possibility that has worked well for many groups in the past is using a Google docs spreadsheet that is accessible by all team members and the tutor. Further notice that for the weekly team meetings and the lecture attendance is mandatory. Failure to show up can result in a deduction of your final grade or your exclusion from this year's course. For the programming, you are required to use the SVN server of the department for version control. Info about this will be given in the 3rd lecture. On the Friday in the first week there is a meeting with the Teaching Assistent for the setup of this repository. In the middle of the project, there will be a deadline when you have to upload your code to the SVN server, so the teaching assistant can give you comments on coding style and documentation. He will also check your final code in order to consider your style and documentation in the final grading.
DELIVERABLE "TEAMS AND TEAMNAMES" (deadline: friday, november 16, 2012 at 11:00)
The teams and teammembers should be decided based on the tutorgroups. This is a procedure that have to be done in conjunction with your tutor. The best thing is to do this during the first meeting on Friday morning with the tutor!
Make sure your list does contain email addresses of all the members in addition to the names and student numbers!!!!
DELIVERABLE "TOPIC" (deadline: friday, november 16, 2012 at 17:00)
You have to decide which game will the original game on which the project will be build.
DELIVERABLE "INITIAL BLOGPOST AND TEAM PAGE" (deadline: friday, november 23, 2012)
In order to promote your team, you are supposed to create an blog/website (that will later serve as the website to promote your game). This blog/site should at least contain a page for your team's name and a short description of each of the team members. You are free to add further infos, e.g. a team logo, info on the game you want to implement, etc. The team member descriptions shouldn't be a full biography, but rather a short introduction of yourself. If you have special skills that will be useful in the game development process (e.g. you are an experience programmer or good at graphics design), you could also mention them.
As of this year the website are created using the blogging service Blogger.com. The blogs will be created by us, you as the students have to fill the pages and make it beautiful!
The first blogpost should contains the aim and topic of your project. Describe the game to be developed, which game was the original game and provide a description/abstract of the analysis.
In addition you need to create a seperate page with the teamname and member-bios.
DELIVERABLE "BLOGPOST ON THE PROGRESS OF THE PROJECT" (deadlines: dec 7, 2012; dec 21, 2012; jan 11, 2013; jan 25, 2013 )
Describe in at least 750 words the progress of the project. Topics for this are free to choose, but need to be related to the project. You can think of these topics (but not restricted to):
DELIVERABLE "ANALYSIS DOCUMENT" (deadline: friday, november 23, 2012)
The analysis document is a document describing what game you want to make, how it works, and what kind of technology is been used (or not used): further info (pdf). As indicated in the related PDF file: the document should be "nice", meaning it should leave a good first impression when you give it to someone. Keep in mind that the results of your project can be the first entry in a portfolio that you will build during your studies and that can help you scoring a job in the gaming industry afterward.
DELIVERABLE "DESIGN DOCUMENT" (deadline: friday, november 30, 2012)
The design document describes how the game will be made, what is necessary for that, what technology is used and its effect on the gameplay, etc.: further info (PDF). As indicated in the related PDF file: the document should be "nice", meaning it should leave a good first impression when you give it to someone. Keep in mind that the results of your project can be the first entry in a portfolio that you will build during your studies and that can help you scoring a job in the gaming industry afterward.
DELIVERABLE "MIDTERM REPORT & CODE (SVN)" (deadline: december 17, 2012)
The purpose of the midterm report is to give yourself an opportunity to reflect on your status and progress so far, identify problems, and if necessary revise and improve your plans. In order to do this, you have to fill out the following midterm report template (DOC). Instructions are given at the beginning of the template. The template can be filled out in Dutch, even if it is written in English.
In addition, you should upload the code that you have produced so far to the SVN server (if you haven't done so already). Make sure that it is well structured, easy to read, and reasonably documented. The TA will have a look at it and rate it according to these criteria (i.e. he will only look on your coding style, not on what you actually have implemented by then). Unless your code is totally horrible, there will be no direct consequences for you. However, you should take this serious, since his comments will help you avoid a negative impact on your grading if we are not satisfied with the quality of your final code (which will be checked more carefully).
DELIVERABLE "MIDTERM PRESENTATION" (deadline: december 19, 2012, 13:15-17:00)
The purpose of the midterm presentation is to have an intermediate evaluation of the project in order to verify and analyze your performance so far, and to identify and avoid potential future problems.
Scheduling & attendance: Before the event, all teams will be split into two groups. The first will present in the time slot between 13:00-15:00, the second from 15:00-17:00. All team members have to be present in their designated time slot (i.e. the whole 2h). You are of course welcome to join the other timeslot as well (i.e. stay for the whole 4h). The schedule and group assignment will be announced on the website in time.
Procedure: Each team has 10 min presentation time: 5 min for a short presentation of their status and plans, 5 min for questions and discussions with the audience. Because of the limited time, the schedule is strict: After 5 min presentation time, we will stop you and start the discussion, which again will stop promptly after 5 min. During this discussion, the following team has to prepare (e.g. get on stage, connect their laptop, etc.), because their presentation starts immediately afterward. There will only be one break within the 2 hours.
Practical issues: The presentations will take place in RUPPERT-ROOD. You can use the data projector and audio installation there. Bring your own laptop and make sure it is working (e.g. you might want to check your laptop on the data projector BEFORE the actual event starts!). If you are not able to bring your own laptop or want to use special equipment, contact the TA about it at least one week before the event. We'll try our best to help you.
What to present: Given the short time, we recommend a short introduction about your goals (1 min), a short demo of your current status (3 min), and a short discussion of your future plans, potential problems, etc. (1 min) that naturally leads to the discussion with the audience. You should aim for "showing something running," e.g. a very first demo of your game that illustrates the idea of both the game and the extension. Of course, depending on your individual goals and circumstances, you might not be able to do this. So, this is not a mandatory, but very strongly recommended requirement. But if you don't have s.th. to show by then, have at least a convincing answer ready when we ask "why not?" ;)
Relevance and impact of your presentation: If you don't do well in the presentation, there will be no direct consequences other than embarrassment and shame for screwing up in front of your fellow students - meaning that you will not get a grade for your presentation. However, it can have an indirect influence on your final grade. It is an opportunity to reflect on your work so far, and, if necessary, revise your goals, change your team organization, identify your weaknesses, and start related actions to improve (including potential revisions of your original plans, if necessary). The more critical you are with yourself, your performance, progress, plans, goals, etc., the more likely it is that you will succeed in the end. Notice that from our side, this is also a good opportunity to identify and sort out "black sheeps," e.g. students who don't contribute enough, but think they can benefit from a good performance of their team mates. For those, there might of course be direct consequences.
DELIVERABLE "REVISED DESIGN DOCUMENT" (deadline: december 21, 2012 (unless otherwise arranged with tutor))
You should schedule a team meeting with your tutor before Christmas in which you discuss your performance so far. Based on your midterm report, your presentation, and your performance as observed in the team meetings, the tutor can then decide that you should (for example) do a complete revision of your design document, write a small add-on specifying necessary changes, write an additional project plan, or (if everything is fine) don't do anything at all (aside from keeping up with the good work, of course). Notice that this is also a good opportunity to not only reflect on the status of the actual product you are developing, but also on how you work as a team and organize yourself (e.g. ask yourself, if you can do things more efficiently, if there are problems in the communication that could easily be solved, etc.).
DELIVERABLE "FINAL REPORT & CODE (SVN)" (deadline: Monday, January 28, 2013, 14:00 GMT+1)
You have to fill out the following report template (DOC). Instructions are given at the beginning of the template. The template can be filled out in Dutch, even if it is written in English.
In addition, you should upload the code that you have produced to the SVN server (if you haven't done so already). Make sure that it is well structured, easy to read, and reasonably documented. The TA will have a look at it and rate it according to these criteria.
DELIVERABLE "PROMOTION MATERIAL" (deadline: Monay January 28, 2013, 14:00 GMT+1)
The promotion material includes
Details for each deliverable:
DELIVERABLE "PRESENTATION & DEMO TO THE JURY" (deadline: Wednesday, January 30, 9:00-17:00 (schedule))
Your game and promotion material will be rated by an independent jury consisting of your tutor and three to four other members. This rating severs as a basis for your final grade (but individual marks can distinguish from it; cf. beoordeling for concrete infos about the grading procedure).
At least a week before the event, a time schedule will be put online. Together with two other teams, you'll be presenting your game to the jury members and answer their questions. In particular, each team gives a 10 min presentation, followed by a 10 min question and answer session for each team (during which at least one jury member will also play your game to see if it works and test the gameplay). Time limits will be strictly enforced. Hence, make sure that your stuff is up and running before your timeslot starts (there will be two rooms, so enough time to set it up, if you come in time).
Considering the presentation, notice that not all jury members know what you've been doing, so make sure to
Considering the question and answer session, the jury can ask you everything about your game, e.g. the actual game play, your concrete contributions, etc. and how you created it, e.g. the actual coding, particular problems that arised, etc. As you can see from the jury's rating form (cf. beoordeling), the major focus is on the end result. But of course, if necessary, issues about team work and the overall procedure could be discussed as well. The rating form should also give you a good idea of what issues you want to focus on in your presentation.
DELIVERABLE "BOX WITH FINAL GAME" (deadline: Wednesday, January 30, 9:00-17:00 (individual time slots TBA))
On the jury day, you also have to have a CD/DVD including cover and box with your final game, source, and all promotion material that you produced. The CD/DVD should have a nice, appealing cover that represents you game and contain:
DELIVERABLE "DEMONSTRATION AT THE SYMPOSIUM" (deadline: Friday, February 1, 13:00-17:00)
The symposium starts with a showcase where each team shows their game and people can walk around and play it. You are expected to setup your game at 13:00. The showcase officially starts at 13:30. Each team member is required to be present during the whole symposium (including the following award ceremony from 15:30-16:30; cf. symposium). Make sure you are well prepared to show and demonstrate your game (visitors can vote for an audience award!). Some team members should always be around at their demo, so people can play it. But you are of course also welcome to walk around and check out what the other teams did (and you can vote for the audience award, too).
Note: teams that are nominated for the best game award (cf. below) will also get a visit from the award committee members during the showcase.
DELIVERABLE "PRESENTATION AT THE SYMPOSIUM" (only applicable to nominated teams) (deadline: Friday, February 1, 15:30-16:30)
After the jury day, five teams will get nominated for the best game award. They will be informed about their nomination in the evening of Feb 1. Nominated teams will get a visit from the award committee during the showcase and have to give a short presentation at the following award ceremony. Details about this will be emailed to them together with their nominations. If you are nominated, you have 1.5 days to prepare you presentation (Januari 31 and the morning of Feb 1).
|(c) Arno Kamphuis|