> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/video-game/project-outline.md).

# Project Outline

Your [project challenge](/cxd/video-game/project-challenge.md) is to design and build a video game that people want to play.

Your team will solve the project challenge by applying a user-centered design process that follows an iterative "Learn-Build-Measure" cycle. In this project, the players of the game are your users.

A key source of information during the game design process will come from **playtesting** — having users play the game in order to get feedback on specific aspects of the game. Playtesting of a game is similar to user testing of an app.

![User-Centered Design](/files/-LDgX8d2pgWnR2DB5SxP)

1. **Research Problem Space** - Let's start by exploring what makes a game engaging and motivating to players. Then you'll explore the elements that help define all games. You'll practice using the Phaser JS game engine to code some sample video games. You'll also practice creating sound effects and animated art for games.
   * [Determine your gamer motivation profile](/cxd/video-game/project-outline/1-1-determine-gamer-motivation-profile.md)
   * [Analyze external motivations in games](/cxd/video-game/project-outline/1-2-analyze-external-motivations-in-games.md)
   * [Analyze internal motivations in games](/cxd/video-game/project-outline/1-3-analyze-internal-motivations-in-games.md)
   * [Analyze game design elements](/cxd/video-game/project-outline/1-4-analyze-game-design-elements.md)
   * [Phaser Practice 1: Code a matching game](/cxd/video-game/project-outline/1-5-phaser-practice-1-matching-game.md)
   * [Phaser Practice 2: Code a top-down game](/cxd/video-game/project-outline/1-6-phaser-practice-2-top-down-game.md)
   * [Phaser Practice 3: Code a side-scrolling game, and create custom assets](/cxd/video-game/project-outline/1-7-phaser-practice-3-side-scrolling-game.md)
2. **Define Problem to Solve** - Your team will identify the gaming motivations and experiences that your game is intended to provide for your target players. Then your team will generate ideas for games that might appeal to these target players. Your team will produce game treatments for several possible game concepts. After evaluating the game treatments with target players, your team will select a final game concept to focus on.
   * [Form project teams](/cxd/video-game/project-outline/2-1-form-project-teams.md)
   * [Create persona for target players](/cxd/video-game/project-outline/2-2-create-persona-for-target-players.md)
   * [Generate game ideas](/cxd/video-game/project-outline/2-3-generate-game-ideas.md)
   * [Refine ideas to create game treatments for top game concepts](/cxd/video-game/project-outline/2-4-refine-ideas-to-create-game-treatments.md)
   * [Evaluate game treatments to select final game concept](/cxd/video-game/project-outline/2-5-evaluate-game-treatments.md)
3. **Design Solution & Deliver Proposal** - Create a game design document, representing a conceptual prototype of your game. Then create a paper prototype of your game to playtest, evaluate, and refine your game's design. Present your proposed game design for critique by other teams.
   * [Draft game design document](/cxd/video-game/project-outline/3-1-draft-game-design-document.md)
   * [Create paper prototype of game](/cxd/video-game/project-outline/3-2-create-paper-prototype-of-game.md)
   * [Playtest paper prototype to refine game design](/cxd/video-game/project-outline/3-3-playtest-paper-prototype.md)
   * [Present proposed game design for critique](/cxd/video-game/project-outline/3-4-present-game-proposal.md)
4. **Build & Develop Solution** - Create a plan to develop a digital prototype of your game design. During development, track your team's progress and any issues that arise. Program your game code in stages, starting with the core game mechanics and iteratively adding, testing, and refining other features. Create and add the visual and audio assets for the game. Create a marketing website to promote your game.
   * [Create development plan for game](/cxd/video-game/project-outline/4-1-create-development-plan.md)
   * [Code game in iterative stages](/cxd/video-game/project-outline/4-2-code-game-in-iterative-stages.md)
   * [Create art and sound for game](/cxd/video-game/project-outline/4-3-create-art-and-sound-for-game.md)
   * [Create marketing website for game](/cxd/video-game/project-outline/4-4-create-marketing-website.md)
5. **Evaluate & Improve Solution** - After creating your game and marketing website, test them with target players to gather feedback and identify possible improvements to make. If feasible, implement improvements.
   * [Evaluate game with external playtesters](/cxd/video-game/project-outline/5-1-evaluate-game-with-playtesters.md)
   * [Evaluate marketing website with user testing](/cxd/video-game/project-outline/5-2-evaluate-marketing-website.md)
   * [Analyze evaluation data to identify possible improvements](/cxd/video-game/project-outline/5-3-analyze-evaluation-data-to-improve-solution.md)
6. **Reflect & Present Project Results** - At a public poster presentation, explain your team's design process and demonstrate your game. Be prepared to respond to questions. Each team member will reflect on his or her project experience.
   * [Create project poster for public presentation](/cxd/video-game/project-outline/6-1-create-project-poster.md)
   * [Present project solution to public audience](/cxd/video-game/project-outline/6-2-present-project-to-public.md)
   * [Write personal reflection on project experience](/cxd/video-game/project-outline/6-3-write-personal-reflection.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.launchboard.app/cxd/video-game/project-outline.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.