top of page

GAME DESIGN DOCUMENTATION

DOCUMENT ORGANISATION

I believe in the importance of staying organised when it comes to

any form of documentation - ease of navigation with documents 

encourages productivity with the project.

Below are examples of document organisation for past project:

IMG_3705.PNG
IMG_3706.PNG
IMG_3701.PNG
IMG_3702.PNG
IMG_3703.PNG
IMG_3704.PNG
IMG_3707.PNG
IMG_3708.PNG
PRODUCTION DOCUMENTS

Generally speaking, I believe that good documentation is an important vessel in the process of game development.
Documents that outline the production plan (such as Backlogs, Sprints/Sprint Plans, Production Breakdowns, etc.) are integral reference points for all team members to understand all aspects of the project.

Below are screenshots of production documents from past projects:

scrum.JPG
pf.JPG
3.PNG
2.PNG
1.PNG
DESIGN DOCUMENTS

Design Documents (such as Concept Overviews, Level Designs, Scripts, Storyboards, Game Treatments, Project Bibles) are fundamental

to the whole project as they are the first pieces of the project that need to be finalised before a project can be started -

they essentially tell the game before it's physically created.

 

Below are screenshots of designs for past game projects:

IMG_3709.PNG
IMG_3711.PNG
IMG_3710.PNG

The Project Bible that I wrote for my major project, is view-able!

LD.PNG
Environment 1.jpg
Environment 2.jpg
bottom of page