Agile

Get Started Using Kanban Cards More Competently

Get Started Using Kanban Cards More Competently

If you are starting to read this post, then you probably already know something about Agile software development and a famous Japanese word – Kanban.

The Kanban methodology is not going to lose its popularity and this post is just about such a small but very important part of the system – Kanban cards.

 

What is a Kanban card?

A Kanban card visually represents a work item – it moves through different stages of completion that are represented on a physical or online Kanban board. This is a key element of the Kanban system that reflects work that has been requested or that is in progress already.

Each Kanban card contains valuable data about the task it represents. It includes the task status, summary of the assignment, deadline, responsible person, and so on. 

The card helps to visualize work, limit work in progress (WIP), and maximize the flow.

In order to quickly understand the idea of Kanban cards, imagine a software development team that use a whiteboard and sticky notes to represent their work items. 

 

What are online Kanban cards examples?

 

As every dev team, they have different features and bugs. They move the sticky notes through defined columns, for example – To Do, Prioritized, Development, Testing, Blocked and Done.

It demonstrates that any Kanban card template is aimed to visualize assignments’ progress from the moment they are requested to the moment they can be considered as done.

During the development process, Kanban cards perform in the following way:

  • inform about every tasks’ step
  • reduce the number of additional meetings
  • improve the transparency of work processes
  • help to avoid context switching as the number of cards that are in progress should be limited.

 

Kanban cards quick history

Any concept has its own history, a Kanban card is no exception.

In Japanese, Kanban means “visual signal” or “signal board.” Kanban cards were invented in the 1940s. Their creator, Taiichi Ohno was an industrial engineer at Toyota company. He was looking for ways to improve Toyota’s manufacturing process and the result of his creation was a Kanban system with convenient cards.

One day Taiichi Ohno discovered an interesting thing during shopping in a supermarket. The supermarket managers re-stocked shelves instead of keeping inventory fully stocked at all times. 

It was obvious that one of the shelves was nearly empty, so the store replenished that shelf with enough merchandise.

Ohno noticed that this kind of just-in-time (JIT) delivery would revolutionize the manufacturing supply chain. He decided to visualize various manufacturing processes on the factory floor. A Kanban card was the great solution right for this aim.

Visualizing the card that included full info about the required quantity, part specifications, and delivery time, suppliers could clearly fill the order and send the restocked bin with its Kanban card back to the factory floor. 

Toyota used this secret for a long time and only in the 1990s, people took notice and the company began sharing the concept details.

 

Types of Kanban cards: physical vs online

When it comes to the modern Agile software development, digital Kanban boards and cards surely look more efficient and beneficial.

Physical Kanban cards limit you in the way how much details and info you can write on each card. It is harder to analyze work item metrics there. 

For this reason, using smart project management software to create online Kanban boards is highly recommended.

 

Kanban cards in software development

 

How does online Kanban card look like?

The typical elements of any Kanban cards are:

  • A title (or a unique item number)
  • Item description
  • A rough estimate of the work size
  • The number of items to be moved
  • Location information
  • Lead time
  • A responsible person
  • The due date
  • A class of service
  • Priority, etc.

 

Kanban cards templates

 

What are the key purposes of Kanban cards?

Kanban cards assist team members to communicate and share information visually, encouraging effective teamwork. They allow to:

  • View important tasks details at a glance. It’s about statuses and due dates, task’s owner and other relevant info.
  • Run deliverables efficiently. With the help of Kanban cards, teams are able to establish clear and consistent expectations for each functional area. 
  • Improve productivity and efficiency. Using Kanban boards with cards you can track lead time that is the time it takes for a work item to go from start to finish. Kanban cards also help to identify bottlenecks in workflow and streamline their process.

 

Using Kanban Cards: key rules and steps

To start working with a Kanban card, you first need to create a board. It does not matter whether it is digital or physical. 

Using a powerful project management tool as Hygger.io, you are able to choose a Kanban board template and customize it to suit your specific project.
This tool looks great for many industries: project management in construction, IT, marketing, finance, education, and many more.  
Define the number of columns you need and what to call them. 

The typical Kanban board example will have three columns: 

  • To-do
  • In progress
  • Done

Then you have to create a Kanban card for every task of your work. It is possible to create a Kanban card template for recurring work items and similar tasks.

After filling the card with the required information, you need to make sure everyone in your team knows how to move the cards through the columns. Everyone is responsible for moving their tasks through the columns, identifying bottlenecks, and making suggestions for improvement.

 

What are the core benefits Kanban cards provide?

 

1. Detecting inefficiencies

Kanban cards easily define when there’s a problem with one of the steps in a work process. The team will quickly get a queue if it consistently has twice as many cards in their Testing column as in Design and Development. The possible solution is to hire more testers.

 

2. Facilitating JIT (just-in-time delivery)

The JIT concept is useful in various industries (not only in the manufacturing sector) including software development. A great solution that helps teams to avoid stagnant projects is a work-in-progress (WIP) limit option. 

It’s important to limit the number of cards on any stage of a workflow at one time. When a Kanban column is maxed out, team members work to move those projects to completion before they can take on new work. 

 

3. Encouraging collaboration

Kanban boards and cards are sharable. As cards advance from column to column, they pass from team to team or from a particular employee to another one. 

Although everybody is responsible for a different part of the process, they all are looking at the same thing and collaborate.

 

What are the risks related to Kanban cards?

  • You should treat a Kanban card like a controlled item because a lost card can cause a shortage. 
  • Kanban cards require stable environment.
  • Outdated cards lead to stock-outs, so try to always keep them updated. 
  • If extra items are hidden, it means that Kanban cards are not showing the correct quantity.
  • Kanban cards manage inventory but do not reduce it.

 

Final words

Kanban cards are aimed to simplify the life of software development teams as they make problems highly apparent. 

If you are not already using Kanban cards, test them first to define all the nuances of their using. No matter what industry you represent, the Kanban system with convenient cards will help you organize your work items and get your job done efficiently. 

If you want to dig deeper into the Kanban world details and its artifacts, study our Agile 101 page.

Rate this post