Initial Configuration
Columns and States
The single most important thing to configure are the states of a board, indicated by the columns.
Setup
The setup is done on the "Configure this project" section:
Then, follow the link to the Columns:
Here you can add a new column and/or reorder the existing columns:
You can also change the column names, edit the dashboard visibility, and delete the columns using the gear option next to their names. These are the basic requirements for configuring the columns.
Configure
The process workflow usually has a superset of the following states, meaning that these are the basic states that most boards contain in one form or another:
- Todo
- Doing (Work in Progress/WIP)
- Done
This is a fine setup in and of itself. However, adding a couple of states makes the workflow much more flexible and robust. The recommended setup for any general board is as follows:
- Backlog/Ideas
- Planned/Prioritized
- In Progress/Doing
- Waiting/Follow-Up
- Review/Testing
- Pending/Time-activated
- Done
There are a couple of other default setups that can be used for other applications. For instance, for a CRM/Sales Pipeline:
- Backlog
- Initial Contact/Offer
- Consultation/Requirements Documentation/Negotiation
- Development
- Demo/Acceptance Testing
- Delivery/Invoicing
- Closed
Or the original use for it, an Inventory Management system. This system uses two boards, one to track the lifecycle of the inventory, and one to keep track of the stock on-hand.
Order Board:
- Order Recieved
- Picked, Packaged, Postage'd
- Currently Shipping
- Delivered
Inventory Stock Board:
- Sold
- To Order
- Waiting
- Recv'd
I will go into a detailed explanation of this on another page.
References and Relevant Links
Kanbanize - 32 Practical Kanban Board Examples
Rows and Swimlanes
Rows - known colloquially as swimlanes - are used to break up the tasks on the board in one of several ways; however makes sense for the particular type of board.
Setup
Configure this project
Go to the "Swimlanes" section
Add, delete or edit a swimlane:
Configuration
There are a couple of rules of thumb when it comes to swimlanes. Use these to indicate priority, with the higher priority towards the top. Don't use these to split up tasks by Assignee - that's what the assignees and filters are for.
Here is the most basic swimlane setup, from top to bottom:
- Critical
- Everything Else
Here is a bit more granular setup with four swimlanes that breaks repetative work into a "Maintenance" swimlane, and splits up "nice to have's" into a column called "Improvements", and bugs/issues/problems into another swimlane called "Incidents".
- Critical
- Incidents
- Maintenance
- Improvements
Similarly to the most basic setup, you can categorize your swimlanes by visibility:
- External Projects
- Internal Projects
This setup is intended to be worked from top to bottom, with tasks moving from the last column of the higher swimlane into the first column of the lower swimlane:
- Onboarding
- Initial Review
- Ongoing Touchbases
Swimlanes are the most efficient way to categorize tasks on a board according to priority or type of task, but I would caution against using them to indicate things that other aspects of the task are meant to indicate (See: Categories, Due Dates, etc.)