> For the complete documentation index, see [llms.txt](https://www.lawfirm-operations.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.lawfirm-operations.org/publications-and-articles/agile-law-firm-workbook/4.-elements/4.4.-tasks.md).

# 4.4. Tasks

<figure><img src="https://827985643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC8LfP0dxThbNkuaHi6Bq%2Fuploads%2FTfIZ8Oxb5s5MzsoLgdv7%2FBildschirmfoto%202024-12-28%20um%2022.00.10.png?alt=media&amp;token=98652e01-bca6-4573-826d-90e534e1bd35" alt="" width="356"><figcaption></figcaption></figure>

Items are next broken down into executable Tasks. Depending on which tool you use to visualize Items and Tasks, Tasks can be a checklist in an Item, sub-Items, or separate cards on a Kanban Board (Chapter 5.1). The Goal of tasks is to make Items easier to handle during a Sprint. A Task usually has a size that allows it to be done within one day.

## Story

### Getting Busy

We have so many Elements described and we’re not yet at the fi nish line, thinks Fiona, wanting to get going on the legal work of the case. Yet, the weeks need to be planned. And plan they do. They find that the description of the tasks was somewhat easier, as they are very near to the actual work to be done. The different sizes of Items trigger questions for our legal team, though: do they need to break down all Items into Tasks or would they leave smaller Items as-is? They initially just seek to avoid doubling the work and therefore only break down tasks that are too big to be addressed at once.

Luckily, they remember that they can start with the fi rst Epics/Items as they occur and do not need to defi ne everything in detail at the start—after all, it wouldn’t be Agile if you knew everything at the start. Phew!

Now that they have arrived at the most detailed Element, they are happy to start their actual work. They quickly agree on who will start with which task. They ask their team’s organizing talent, Oliver, to arrange another meeting with the client’s project manager, Caleb, and ask him if there are key people that need to be involved. Senior associate Fiona will take the task of creating an overview of all involved parties, but she still has mixed feelings about their process. It is an interesting experience, yet they could have started earlier without it, likely with a similar allocation of Tasks. Gabriel will need to do more preparation for their Agile methods—something they certainly need as a fresh team, but which is not part of the core work they need to do for a client.

## Example

### Item 2: Draw an overview of all parties involved in the case

Tasks:

* [ ] Organise a meeting with the client.
* [ ] Gather a list of all parties (based on discussion with client).
* [ ] For every party, note their function.
* [ ] Sketch their relations.
* [ ] For each party, note their position.
* [ ] Confirm the details with client.
* [ ] Establish their interest in the case.
* [ ] Establish their influence on the case.
* [ ] Update the stakeholder map accordingly.

## Template

**Item: ...**

**Title: ...**

<figure><img src="https://827985643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC8LfP0dxThbNkuaHi6Bq%2Fuploads%2Feygj0OSOROhIL4CdI9mH%2FBildschirmfoto%202024-12-28%20um%2022.06.26.png?alt=media&amp;token=dcfac701-1bb8-45df-b438-320ec8a4ddfd" alt="" width="131"><figcaption></figcaption></figure>


---

# 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://www.lawfirm-operations.org/publications-and-articles/agile-law-firm-workbook/4.-elements/4.4.-tasks.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.
