Skip to content

Changes

Page history
Update game project instructions authored by Paavo Nelimarkka's avatar Paavo Nelimarkka
Show whitespace changes
Inline Side-by-side
game-project-instructions.md
View page @ fa33348e
...@@ -45,16 +45,16 @@ In the end you should have: ...@@ -45,16 +45,16 @@ In the end you should have:
* Game Design Document (10-40 pages) * Game Design Document (10-40 pages)
* Game Project Plan * Game Project Plan
* Review (test), memos from internal meetings, and other documents during the development phase * Review (test), memos from internal meetings, and other documents during the development phase
* Presentation (see below; utilize your game project website/github) * Presentation (see below; utilize your game project website/gitlab)
* Final report (lessons learned; post-mortem): what did you learn, what went wrong, what went right => best practices; self-evaluation (process, outcomes); improvement suggestions (for yourselves and for this course); self-evaluation (grade for the project group and, if you want to emphasize the effort of someone or for some other reason to divide the grade, personal grade suggestions; and continuation plan: what shall you do next (new platforms, levels etc.) * Final report (lessons learned; post-mortem): what did you learn, what went wrong, what went right => best practices; self-evaluation (process, outcomes); improvement suggestions (for yourselves and for this course); self-evaluation (grade for the project group and, if you want to emphasize the effort of someone or for some other reason to divide the grade, personal grade suggestions; and continuation plan: what shall you do next (new platforms, levels etc.)
If you want, you can create just one document containing both the project plan and game design. We strongly recommend using wiki (Github) for your game development. You can choose the tools you need in your game development project (e.g. Bugzilla, Testlink etc.) helping to keep your game project related information up-to-date. If you want, you can create just one document containing both the project plan and game design. We strongly recommend using wiki (Gitlab) for your game development. You can choose the tools you need in your game development project (e.g. Bugzilla, Testlink etc.) helping to keep your game project related information up-to-date.
# 3. Production: create your game (prototype) # 3. Production: create your game (prototype)
You should be aware that normally developing a full-featured game takes time (sometimes several years). In this course, you have only a couple of months to finish your first game. Therefore, try to build a prototype containing only the core features (so called minimum viable product, MVP) first. It is a good practice to illustrate your idea (e.g. by creating UI mock-ups) and get feedback from your friends and actually from anybody who is willing to offer their time to evaluate your game idea. You should be aware that normally developing a full-featured game takes time (sometimes several years). In this course, you have only a couple of months to finish your first game. Therefore, try to build a prototype containing only the core features (so called minimum viable product, MVP) first. It is a good practice to illustrate your idea (e.g. by creating UI mock-ups) and get feedback from your friends and actually from anybody who is willing to offer their time to evaluate your game idea.
# 4. Check that you have done everything # 4. Check that you have done everything
You can and should use [checklists](https://github.com/JAMK-IT/TTOW0211-221-game-development/blob/master/checklists.md) provided by H. M. Chandler in the Game production handbook. You can and should use [checklists]() provided by H. M. Chandler in the Game production handbook.
# 5. Final presentation & Video Demo # 5. Final presentation & Video Demo
... ...
......