Pattern: KANBAN
Problem: Situations or projects in which we need to manage tasks, handling how they evolve, and monitoring them. In this way, we need a full vision of the tasks that make up a project and we need to know at each moment which is the status of each task.
Motivation: This pattern will be used for representing the state of the tasks of a project when the state of each task to be done and the amount of task in each state is relevant: for managing the correct evolution/rithm of the project, to manage the resources needed in each state, etc. In addtion, some projects also require to perform several steps to finish a task, being the state of the tasks relevant for the reasons shown previously.
One of the most frequent uses of this pattern is the collaborative management of the tasks of a project. Depending on the complexity of the tasks, it’s probable that they go through different phases before completing the process. The minimum of this is having three state: “to do”, “doing” and “done”, but there may be intermediate stages, as “design”, “code review” or “testing”. With a kanban pattern the user will have a global vision of the project, letting the user know how many tasks are in each state. It could be useful for applying effort balancing techniques and reduce bottlenecks, controlling the maximum number of tasks at each phase.
Solution and graphic representation: Each list represent a possible state (phases, steps…) of a task in the context of our problem. We will have as many lists as different states. Tasks will be represented by cards. Initially, cards are storaged in the first bucket (usually called “to do”) as tasks are storaged in a backlog. Tasks will flow through the lists as long as they are in progress or finished in real life. Kanban board will represent in this way the state of every task at any given moment.
Related Patterns:
Kanban pattern differs from “Assigned Tasks” only in the presence or absence of order between lists. This will make you to choose one or another depending on if you want to have a view of the status of the tasks of the project, or if you prefer to focus on who is the responsible of doing it.
In addition, Kanban differs from “Process Tasks” in the presence or absence of card flow. This means that in the first pattern we will represent the process to know in real time the status of each task, while with the second pattern we will have an static view of the tasks that we should do to complete the process, as in a recipe.
Kanban is usually combined with “Categorized Information” pattern. It enhances the usability of the pattern, because it adds extra information or some resources of the project, allowing the user to better understand the whole process than if we have only the tasks, without explanation.
Example:
![image](https://user-images.githubusercontent.com/47741431/110635377-50356780-81ab-11eb-9697-cfddfb6e70b0.png)
In this template we have a linear and conventional Kanban pattern, with the peculiarity that it has multiple intermediate phases, as “design”, “code review” or “testing”. Tasks will advance linearly as they go through these states in real life and they complete the whole process.
Trello Templates Examples:
- 5 Product Management Buckets
- Agile Board
- Agile Sprint Board
- Decision Tracking Board
- Incoming Requests
- Innovation Weeks
- Learn a Language
- Lifestyle Goals (Living Room Remodel)
- Managing Translations
- Marketing Overview
- Marketing Requests
- Mise-En-Place Personal Productivity System
- Moving Plan
- Office Party Planning
- Post-Mortem Meeting Board
- Product Launch
- Product Roadmap
- Productivity Workflow
- Project Management
- Research Iteration
- Site Reliability
- Team Organization Central
- Wedding Party
- Wedding Planning
- Where to next? Travel inspiration board