> For the complete documentation index, see [llms.txt](https://docs.idew.org/project-video-game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idew.org/project-video-game/project-instructions/2-design-and-build-solution/2.8-solution-presentation.md).

# 2.8 Solution Presentation

{% tabs %}
{% tab title="✓ TASK" %}
Create a **slide presentation** that explains and demonstrates the video game that your team designed and developed. The presentation is an opportunity for other teams to ask questions and provide feedback to help your team improve its game.

Your team's presentation should include the following (in this order):

1. **Project Team:** game's working title, team name, team members & their roles
2. **Gaming Motivations and Player Experience Goals:** Describe the targeted gaming motivations and player experience goals for the game.
3. **Game Concept:**  Briefly explain the premise, setting, characters, story, objective, and conflict of your game. Be sure to include concept sketches.
4. **Paper Prototype:**  Show the video demonstrating your paper prototype gameplay. Narrate the gameplay to explain key features.
5. **Paper Prototype Playtesting:**  Briefly summarize the key issues discovered during playtesting and the design changes made to address the issues.
6. **Video Game Demonstration:**  Provide a live (or recorded) demonstration of your video game. Narrate the gameplay to explain key features.

The presentation should have 6-10 slides and take 5-10 minutes to deliver.

* Be sure to practice your presentation before delivering it to your class.
* Be sure to record notes on any constructive feedback your team receives.

### **❏ Deliverable**

Submit your team's slide presentation
{% endtab %}

{% tab title="★ RUBRIC" %}

| **✓- Below Standard** | **✓ Meets Standard** | **✓+ Exceeds Standard** |
| --------------------- | -------------------- | ----------------------- |
| Description           | Description          | Description             |
| {% endtab %}          |                      |                         |
| {% endtabs %}         |                      |                         |


---

# 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.idew.org/project-video-game/project-instructions/2-design-and-build-solution/2.8-solution-presentation.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.