> For the complete documentation index, see [llms.txt](https://program.hackyourfuture.dk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://program.hackyourfuture.dk/course-content/foundation/final-project/session-plan.md).

# Session Plan

## Session Outline

This module is designed to be ran as a three week project. That means there will be three sessions, but it doesn't have the usual structure of content and learning goals for each week.

Instead, trainees will be continuously working through the [Project Brief](https://program.hackyourfuture.dk/course-content/foundation/final-project/project-brief.md), which is split up into three weekly milestones.

### The first session

Note: Trainees will work in pairs to compelete the project. These pairs will have been organised by a staff member before the session.

* Introduce the project requirements outlined in the [Readme](https://program.hackyourfuture.dk/course-content/foundation/final-project.md) and answer any questions.
* Remind trainees to use the project management skills they have recently learned. The [Readme](https://program.hackyourfuture.dk/course-content/foundation/final-project.md) describes these "organisational requirements" of the project that must be met.
* Give space for the trainees to organise into their pairs and get started.
* Actively work your way around the pairs, making sure everyone is making progress as they should.
* If multiple people are facing similar challenges, take the opportunity to "pause" the session and walk through something together out loud (e.g. creating a new github repo).

### The second session

* Progress update: Check in on what people have completed since last week, what they found hard, questions to answer, and encourage some people to demo their progress in front of the team.
* Teaching moment: If there were any significant issues or confusions that came up, spend some time diving into them in detail.
* Introduce the next milestone: Talk through the next requirements in detail, and answer any questions.
* Pairing time: Allow space for the trainees to continue working on their project, answering any questions as they come up with the whole team.

### The final session

The final session acts as a showcase for the projects. Here is an outline that can be shared with trainees:

```plaintext
🎮 Final Project Presentation Guidelines
When: 3rd week of the Foundation project
Duration: 7–10 minutes per team

Presentation structure:

1. Start with your Trello board → Explain your workflow, task organization, and process.

2. Show your project → Demonstrate the working game/application.

3. Talk about contributions → Each team member should briefly explain what they worked on.

Requirements before presentation day:
✅ Project must be fully deployed and live.
✅ Prepare a QR code linking to your live project.

During the session:

Share the QR code so other teams can test your game on their devices.
```

### The final assignment

After the presentation, trainees will have recently received lots of feedback and ideas for improving the app. Each trainee should choose 1 (or more) improvement to implement as a follow up assignment. The size of the change is not so important, since a small code change can significantly improve the app or fix a bug. The important part is that they choose a valuable change from the feedback and implement it.

This helps close the feedback loop from the last session, and provides closure for the final state of the project before completing the course.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://program.hackyourfuture.dk/course-content/foundation/final-project/session-plan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
