PLANNING TEMPLATE

Game project brief

A brief that names the decision, scope and people needed to start a useful game-development discussion.

How to use this resource

Copy the template into your working document. Add what is known, mark unknowns and identify who can resolve them. No email is required.

What to include

Project and intended user

Record the relevant facts, owner or open question.

Current build, engine and version

Record the relevant facts, owner or open question.

Next milestone and decision

Record the relevant facts, owner or open question.

Player flow and bounded deliverables

Record the relevant facts, owner or open question.

Target platforms, devices and input

Record the relevant facts, owner or open question.

Acceptance scenarios and acceptance owner

Record the relevant facts, owner or open question.

Repository, assets, licenses and dependencies

Record the relevant facts, owner or open question.

Client, delivery, QA and third-party responsibilities

Record the relevant facts, owner or open question.

Review builds and change control

Record the relevant facts, owner or open question.

Source files, build instructions and handover

Record the relevant facts, owner or open question.

Unresolved risks and next action

Record the relevant facts, owner or open question.

Version 1.1 · Editable plain text (.txt) · No email required

Download the resource ↓
View completed sample — fictional example
SAMPLE — fictional planning example, not a Fluxoraa client project.
Project: one menu flow in a prototype.
Decision: can a first-time player start and replay with a controller?
Target: one agreed PC configuration.
Acceptance: start, pause, resume and restart work in a packaged build.
Owner: the project reviewer (to be assigned).
Excluded: full game production, online accounts and console submission.

Discuss your completed brief

Discuss your completed brief