Using the Kanbanboard View

We already had a look at the Contextchart view mode in the previous chapter.

The Contextchart view is, simply speaking, a rendering of topics as "boxes within boxes” (depending on the parent of each topic), with the ability to individually influence rendering on horizontal or vertical alignment.

In contrast, the Kanbanboard view primarily sorts the topics by their states and aligns them horizontally, in clearly identifiable columns:

(Example of the kanbanboard view in Zingoolarity)

Topic which do not have a state yet, are rendered in the "Backlog” column.

All other aspects of the Kanbanboard view are identical to the Contextchart view.

You can dynamically switch between the different views by clicking on the buttons on the left side of the breadcrumb.

Kanbanboard within Kanbanboard

You can dynamically drill into one of the tasks on the Kanbanboard and directly use the task as another (Sub-) Kanbanboard, if the need arises.

Overall, you can use any topic anywhere in topicspace as a Kanbanboard without any preparation.
This is a key strength, as you do not need to setup a lot of complicated things; just go ahead and focus on the content.

For what can you use the Kanbanboard view?

The Kanbanboard is a good way to track simple tasks, which are not planned on long-term scale (for example for ToDo lists).

It is a good practice for periodic quick planning together with a team by

• reviewing the state of running topics,
• completing tasks after checking the results,
• moving tasks from the backlog to "running” for the next cycle (e.g. a week).

As soon as you need more "planning ahead”, the final Roadmap view mode is the right choice.

The Roadmap view mode is explained in the next chapter.