> 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/intro-to-agile/week-1/assignment.md).

# Assignment

Now it's time to practice planning a project and prioritising tasks on your own!

## Instructions

1. Imagine you are building a new personal portfolio website. Think about the kinds of set up, features, content etc. that would be required to bring it to life.
2. Create a new Trello board using [the same columns as you did in the session exercise](/course-content/foundation/intro-to-agile/week-1/session-plan.md#prioritising-tasks) and brainstorm a list of at least 10 tasks to implement the projet.
3. Prioritise each task into the **Now**, **Next** and **Later** columns and order the tasks accordingly.

## Tips

* You're only *planning* a project here, so expect the "In Progress" and "Done" columns to be empty for now.
* There's no right answer for e.g. how many tasks you prioritise into the first sprint, but check out these guiding tips to stay on the right track:
  * **Now** - Tasks to complete in the first sprint (e.g. first week). These will likely be set up tasks and end in the first working version of your portfolio.
  * **Next** - Tasks to complete in the next sprint (e.g. next week). These will likely be adding/finishing the main features of your portfolio.
  * **Later** - Tasks to be prioritised at a later date (e.g. some time in the future). These could be optional ideas, improvements or new features to explore later.

## Submission

Submit your assignment as a PR as usual. Add your board's public link to a simple text or markdown file.


---

# 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/intro-to-agile/week-1/assignment.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.