> 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/3-evaluate-and-refine-solution/4.1-public-presentation.md).

# 3.5 Public Presentation

{% tabs %}
{% tab title="✓ TASK" %}
Your team will **explain and demonstrate your project solution to a public audience,** which might include professionals from industry, college, and your school – as well as parents and fellow students. Some audience members might be acting as judges reviewing the team projects. Many audience members may be learning about the project for the first time.

Your team's presentation needs to tell a complete story (with a beginning, middle, and end) in just a few minutes. The presentation should be clear, concise, engaging, and professional.

* Plan and practice your team’s presentation and demonstration
* When helpful, refer to your poster and product website during the presentation
* Be sure to allow the audience to examine and interact with your project solution
* Be prepared to answer questions from the audience
* Be prepared to adapt if a technical issue occurs during the demonstration

## **❏ Deliverable**

Participate in your team's presentation and demonstration at the public event
{% 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/3-evaluate-and-refine-solution/4.1-public-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.