Game Development Reference
In-Depth Information
8. Test Plan
9. Project Plan
Manpower Plan
Resource Plan
Project Tracking Doc
Development Schedule
Milestone Definitions
10. External Events
11. Current Risks
12. Credits List
13. Change List & Project Archives
High Concept Document
This is a very short document, no more than a few sentences, which answers the ques-
tion, “What is your game about?�? See Chapter 5 for more details and examples. It may
seem strange to devote an entire document to this brief topic, but it's important to do so.
Like a company's mission statement, it's useful to print this up and post it around the
office so everyone has a visible reminder of what they're trying to create. It should also
be maintained in a prominent place on the organization's internal Web.
If the high concept changes while the game is in development, that's a major event that
should receive a lot of attention. If this happens, make sure to update this document
and post new copies where everyone can be reminded how the basic course of the pro-
ject has changed.
Game Proposal (“Pitch Doc�?)
This is the one- or two-page executive summary of the game that you give to prospective
publishers during your pitch meeting. Ideally, it would be accompanied by a playable
prototype of the game, as well as a more complete concept doc (see next section).
The game proposal document should have the following sections:
1. High Concept. The one- or two-sentence statement of the experience you're
trying to create.
Search WWH ::

Custom Search