> 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/5.-kanban.md).

# 5. Kanban

Now for one of the most popular and most versatile tools used in Agile working: Kanban. Kanban can be immensely useful to visualize work and create transparency. It essentially stands on its own and can even be used out of an Agile context. No matter whether you are using classic project management (e.g. waterfall), Agile or any other form of organising, in many cases Kanban can be beneficial.

The basic idea behind it is to simply visualize the path that every single Element goes through, from start to finish. For that to work, Kanban uses board with cards to visualise their status. The change of the cards’ position reflects the development in the process.

In an ideal scenario this means that you can identify bottlenecks in your process very quickly and can start to improve it to achieve better flow, leading to a more efficient process. As a result, it is one of the favourite tools of many Agile teams.

There are many use cases in which Kanban could be used. Who knows, maybe your marketing team is already using one to organise their workflow or to schedule creating and publishing content?

In this chapter we will guide you through the basics behind Kanban so you can start experimenting with it right away.


---

# 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/5.-kanban.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.
