How to create a Kanban Board

How to Create a Kanban Board: A Practical Guide

Visualization of your workflow is one of the primary practices of Kanban. A good Kanban board helps you track your progress and spot blockage points in your workflow at a glance. This transparency will enable you to improve your work stages, your workload, and your efficiency. However, if you search for Kanban board examples, most of the time they are not a good fit for your specific needs, especially if you are working in a non-IT area.

How to design your Kanban board

The very first Change Management Principle of Kanban states, “start with what you do now.” However, this can be overwhelming if you own multiple different types of projects and tasks. 

Recommended for you: Kanban Foundations online course

It’s always a good idea to collaborate with your team members and utilize the group’s wisdom. A quick guided brainstorming session will help you gather the information you need, so you can reflect this on your board effectively and creatively. Keep in mind that the board will be an essential part of your working day, and it needs to be updated regularly by your team members. That’s why it’s crucial to come up with a board that is easy to understand and update. If you overcomplicate things, it will have a negative impact on efficiency and discourage your team members from using it correctly. However, don’t worry if you don’t get it perfect the first time: creating a Kanban board is an iterative process and you will be able to improve it over time. 

Step 1: Ask the key questions

Before starting to lay down your daily tasks and processes, first, align on some key questions.

  • For whom are we designing the board? Is it only for our internal purposes, or will our stakeholders also benefit from it? 
  • What are the most critical points for us? What do we want to see with the first look? The workload? The blockers? Status of individual tasks?
  • How detailed shall the individual cards be?
  • How frequently are we going to update the board? As soon as a task changes the status or is it acceptable for us to update it daily?

Kanban online course

Step 2: Discuss the processes and tasks

After aligning on those answers, you can move on to the next step and start talking about your processes and tasks. Ask everyone to think and write about their steps after a task appears.

  • Where do you collect information and the tasks?
  • Are there any waiting points? Any approvals? Any dependencies where you can see patterns?
  • Do you have team members who have different roles? 

Depending on the nature of your tasks, you may have different steps. It will be easy if you draw a flowchart. If you are a customer care team, your flowchart is probably similar to this one:

Step 3: Group the tasks and start to visualize the process

You may want to group some of the steps under a single column. One thing to keep in mind, avoid back and forth travel of the tickets. They need to always flow in one direction. If you’re going to visualize the status of each customer request, your board can look like this:

You can choose different colors for different people and use initials or avatars to indicate the task owner. It’s also another Kanban practice to limit the work in progress (WIP), to finish the tasks at a certain pace without creating a crowd in specific steps. Monitoring the times of the individual cards will help you to improve your cycle and lead times.

Recommended for you: Make the process fun with the Kanban Pizza Game

If all your team members are doing their tasks in a similar pattern, it’s easier to visualize this. But if you have different responsibilities within your team, recommend grouping them. For example, you may use different “swimlanes” for different roles or subteams. 

It’s also possible to create consecutive blocks, which is helpful if your tasks are more complex and need to be segmented. 

It’s a good practice to indicate blocked items, for example with a different card color or with an extra marker, as indicated below.

You don’t always have to use columns and rows. You can get creative and design your board as it will suit you best. Let’s say it’s essential for you to see the distribution of the workload for equally important, parallel tasks. In that case, a pie chart may represent your workflow better than a table would. 

Of course, you may combine them, too. If you can utilize physical boards or walls, it will give you more flexibility compared to a standard tool like Jira or Trello.

Download our free Miro templates to copy and modify for your needs.

Want to learn more about Kanban?

Kanban is a workflow management system that can help you visualize, streamline, and improve on your processes in the workplace. But there’s more to it than simply creating a board. Learn about it in our Kanban Foundations online course, or take a look at our webinars, which cover a broad range of topics on Agile, Scrum, Kanban, and just about anything else that relates to improving the workplace. There are also a number of agile42 training options, both in-person and remotely, which can transform the way you work: 

If you need some more help getting your team started in Kanban methods, check out our Kanban Start-Up Package, which includes dedicated in-person coaching as well as Kanban training. 

Join our free agile42 Community and gain access to thousands of agilists from all over the world to share experiences, challenges, and ideas. A safe and moderated community of like-minded people, who share a passion for all things agile – organizational culture, lean and agile methods, coaching & more!

Please do get in touch with us should you have any questions – we would love to hear from you.

Follow us on our social media platforms:

LinkedIn | Facebook | Twitter

 

Step up your Kanban game

With the growth of knowledge work, such as professional services, creative industries and the design of physical and software products, there is a growing interest in managing work using the Kanban method. The focus of Kanban is the delivery of services by an organization – one or more people collaborating to produce (usually intangible) work products. Even where there is a physical product from services, value resides less in the physical item itself, and more in its informational content (the software, in the most general sense).

The method is based on the concept of a kanban system – a delivery flow system that controls the amount of work in progress using visual signals. The challenge is moving from a so-called “Proto-Kanban”, where teams just put work items on a board, towards a true Kanban organization.

A number of agile42 coaches are Accredited Kanban Trainers (AKTs) from the Lean Kanban University and will deliver training classes in the upcoming weeks that put the participants on the path to be certified as Kanban Management Professionals (KMP). The KMP I class is the first step toward the credential showing you have had top quality Kanban training in order to launch and manage Kanban initiatives.

In this round of classes we meet our future KMPs in new locations, including our first ever certified Kanban training in Rome and in Toronto:

and more dates available soon. Students from KMP I classes can proceed to the KMP II class that delivers the KMP certification. At the moment we have one class scheduled, with more to be organized later in the year:

As always, check our full list of training classes for an opportunity near you.

All videos from Lean Kanban Southern Europe 2014

Lean Kanban Southern Europe 2014 has been a great success in Bologna on May 30th. A packed room of attendees that gathered in the Italian town to listen to the top presenters of the Lean and Kanban movement – and they also played Kanban Pizza Game with agile42 coaches!

agile42, as the organising sponsor of the event, has produced video recordings of all session that you can watch here (using a YouTube playlist) or in a specific page together with slides.

agile42 invites you to Lean Kanban Southern Europe 2014

We are happy to welcome the Lean Kanban global conference series to Italy! The Lean Kanban Southern Europe conference brings together professionals who realize the value of Lean thinking. This is the event for technology managers, business leaders, and change agents who want to build quality, predictable delivery, and a culture of continuous improvement into their organizations.

Part of the Lean Kanban global conference series, it’s been scheduled on a one-day format that will accommodate networking and participation from a diverse set of attendees.

The program is under development but already includes David J Anderson, Bjarte Bogsnes, Jabe Bloom, Joakim Sundén and many other speakers. This will also include the Lightning Talk presenters that are replying to our ongoing Call for Participation. Join us to share your experience on stage!

Looking forward to seeing you in Bologna on May 30!

You Don’t Need to Change. Survival is Optional

The title refers to a quote attributed to W. Edwards Deming.

Today there’s general consensus – and a lot of noise – about the need for change. Still, organizations are having a hard time with change. Most change initiatives fail. Sometimes it’s just a matter of lack of will to change. Sometimes organizations just don’t even understand why or what they have to change.

Change is often believed to be magically reachable designing new processes on paper, possibly paying huge amounts of money to consultants.

The talk introduces the Kanban Method (not to be confused with the Kanban Tool) as an evolutionary approach to managing change and as a way to build a learning and adapting organization.

 

printed sticky notes glued on board

Kanban for Portfolio Management 
talk at OSS4B in Prato

On September 19, I gave a talk at the Open Source Software for Business conference in Prato.

The Conference has been very well organized and I had the honor to share the stage with the likes of Gene Kim (author of The Phoenix Project book), Dragos Dumitriu (the ‘hero’ manager described in David J Anderson’s Kanban book) and many others.

Slides for my talk Kanban for Portfolio Management are available here.

stainless steel tool on gray sand

Kanban and Scrum

In August last year Gartner signalled the death knell of Waterfall. All the evidence over the last 25 years points to some form of Lean-Agile method as the only sensible way forward for managing knowledge work. Kanban and Scrum (together with eXtreme Programming) are the pre-eminent Lean-Agile methods. I would argue that any investment you make in learning these will be the best investment you can make for your career and also the best investment your organisation can make in ensuring business sustainability in the long-term.

You might think it strange that a company named Scrum Sense would talk about Kanban. The truth is that Kanban was a baby in diapers when Scrum Sense started, while Scrum was already the de facto standard in the Agile world. When Maritza van den Heuvel approached me in November 2009 about the possibility of hosting David Anderson in Cape Town I jumped at the opportunity. He visited early in 2010 and we had a great time exploring this new process with him. We learned a lot and I’m tempted to say that we also helped clear up some mis-conceptions about Scrum.

Three years have passed and Kanban now has a significant presence in the Lean-Agile world. The latest worldwide Agile survey places Scrum and Scrum hybrids (most commonly Scrum + XP) first with 66% of the Agile market and Kanban second with 24%. Impressive growth in just about 5 years. Why is this?

As usual, there are some good and some bad reasons. Let’s start with the bad. Many organisations that attempt to ‘do’ Scrum are not actually willing to make the adjustments to their ways of working, ways of managing and company culture that are needed to realise the hoped-for benefits. Scrum is not the silver bullet they hoped for. So some look for the next shiny thing…and discover Kanban. By now, a number of these organisations have also dumped Kanban in search of something easier. One client of mine who did this has largely gone back to Scrum.

There are good reasons too. I see organisations trying to use Scrum to manage work that is really not complex, sometimes repetitive and whose arrival rate is highly variable. Not conducive to being planned in week- to month-long fixed increments. Much more suited to being handled using clear policies and SLA’s.

By now you are asking yourself what the differences are between these to Lean-Agile methods, and where to use what. This is, naturally, a non-trivial question. A good starting point to seek answers is Henrik Kniberg and Mattias Skarin’s free mini-book.

My message is this: if you want to be equipped to make good decisions in the future Lean-Agile world you need to educate yourself in both Scrum and Kanban. And along the way you will realise that you need to develop your so-called “soft” skills and learn how to manage organisational change too.