What is Kanban? Here’s what your Agile team needs to know

Julia Martins contributor headshotJulia MartinsJuly 18th, 20229 min read
facebooktwitterlinkedin
What is Kanban article banner image
View Templates

Summary

Kanban is a well-known Agile management methodology. To use the Kanban framework, your team will implement a philosophy of continuous improvement, where work items are “pulled” from a product backlog into a steady flow of work. The Kanban framework comes to life via Kanban boards, a form of visual project management that help your team visualize work moving through stages. Learn more about the Kanban methodology and how you can use it on your team.

Imagine: Your team is embarking on a new project. You need an easy way to visualize work so you can stay up to date on who’s working on what, what stage work is in, and when everything is due. You could scroll through your project documents, spreadsheets, emails, and messages to cobble together that insight—or you could view it all in one place with a Kanban board.

If you’ve dabbled in project management or started exploring ways to visualize your work, you may have heard of Kanban. Kanban helps teams balance the work they need to do with the available capacity of each team member.

This article covers everything you need to know about what Kanban is, how Kanban boards work, and how you can best use them to manage your team’s work.

What is Kanban?

Kanban is an Agile management method built on a philosophy of continuous improvement, where work items are “pulled” from a product backlog into a steady flow of work. The framework is applied using Kanban boards—a form of visual project management. In a Kanban board, tasks—represented as cards—move through stages of work—represented as columns. That way, your team can see where work is in real-time.

Kanban is especially popular with product, engineering, and software development teams. But they can be used by any team that’s interested in building a more dynamic, flexible workflow.

Free Kanban board template

History of Kanban

Kanban was developed by Taiichi Ohno, a Toyota engineer from Japan, in the late 1940s. Ohno realized he could improve the Toyota Production System by incorporating elements of lean manufacturing: Instead of building new products based on anticipated demand, Ohno’s Kanban framework—also referred to as the “Just-in-Time” (JIT) system—produced and re-supplied products as a result of consumer demand. The new framework transitioned the Toyota manufacturing process from a “push” process (products are pushed into market) to a “pull” process (products are created based on market demand). This meant that Toyota could have a lower inventory level while still being a competitive player in the market.

“Kanban” is a combination of two Japanese words: 看 (Kàn), meaning “sign,” and 板 (Bǎn), meaning “board.” 

Though Kanban still lives on in many manufacturing settings, it was adapted for software development in the early 2000s. Inspired by Ohno’s lean manufacturing methodology, Kanban for software development also implements the same “pull system” process that Ohno’s lean manufacturing did.

What is the difference between Kanban and Scrum?

You may have heard of Kanban in conjunction with Scrum—in fact, most teams that run Scrum do so on Kanban boards. Scrum is compatible with Kanban but it is a different framework:

  • Scrum helps teams get more work done faster. The method organizes work into “sprints”—two-week working sessions with daily meetings and a set amount of work to be completed during the cycle time.

  • Kanban helps teams improve processes by visualizing their work in real-time.

Read: Scrumban: The best of two Agile methodologies

What is the difference between Kanban and Agile?

Kanban for software development is a subset of Agile. Here’s how they differ:

  • Agile is a project management model designed to help teams flexibly respond to change. The Agile philosophy believes in adaptive planning, evolutionary development, early delivery, and continuous improvement.

  • Kanban processes are shorter and fit sprint boundaries.

Read: Waterfall vs. Agile vs. Kanban vs. Scrum: What's the difference?

What are Kanban boards in project management?

Kanban teams use a visualization tool called Kanban boards to manage their workload and flow.

In a Kanban board, work is displayed in a project board that is organized by columns. Traditionally, each column represents a stage of work. The most basic Kanban board might have columns like “To do,” “In progress,” and “Done.” Each column is filled with visual cards that represent individual tasks. A team moves through the columns until the tasks are completed.

Picture it like the shelves in a supermarket. As product inventory diminishes because it’s bought by the consumers, staff refills the shelves with new products. The shelves are never empty but the product is constantly replaced with new items—a Kanban board is continuously filled with new tasks as your team completes old ones.

Now, you can have a physical Kanban board hanging in a conference room or you can streamline processes online—a much easier solution for remote or virtual teams.

Virtual Kanban boards

Today, you can create and maintain your Kanban board online. Virtual Kanban board tools help you dynamically visualize content and get at-a-glance insight into your entire project’s work. Oftentimes, teams use these virtual Kanban boards, like Asana’s Board View, to visualize work moving through stages:

[Product UI] Project plan template - work requests template (Boards)
Free Kanban board template

How Kanban works

Whether you draw your Kanban board on a whiteboard and use sticky notes for each task or streamline your workflow virtually—the framework works wonders when it comes to optimizing your team’s work. You just have to learn how to keep it rolling. 

Each “card” within a Kanban board represents a task. Your team moves the task cards through the stages of work until they’re completed. Teams that use a Kanban system tend to collaborate on a single Kanban board, though you typically assign tasks to individual team members.

The 4 core principles of Kanban

There are four core principles to help guide your team as you think about rolling out a Kanban framework:

[inline illustration] The four core principles of Kanban (infographic)

1. Start with what you do now

You can apply Kanban to any current workflow or process. Unlike more defined Agile management processes like Scrum, Kanban is flexible enough to work within your team’s core practices.

2. Agree to pursue incremental, evolutionary change

Big changes can be disruptive to your team—and if you try to change everything at once, your new system may not work. Kanban knows this, which is why the Kanban framework indexes on continuous improvement and incremental change. Instead of changing everything all at once, start by pursuing incremental change in order to truly evolve your team’s processes over time.

3. Respect the current process, roles, and responsibilities

Unlike other lean methodologies, Kanban doesn’t have any built-in team roles, so it works within your current team structure and process. Additionally, your current process may have some great elements, which would be lost if you attempted to completely revamp your working system in one day.

4. Encourage acts of leadership at all levels

In the spirit of continuous improvement, the Kanban method recognizes that change can come from anywhere—not necessarily just “top-down.” With Kanban, team members are encouraged to chime in, brainstorm new ways for processes to evolve, and take the lead on new work initiatives.

The 6 practices of Kanban

The Kanban core principles help guide your team’s mentality when you approach the Kanban workflow. To implement a Kanban process, follow these six practices to help your team continuously improve and achieve incremental growth—the core tenets of the Kanban framework.

[inline illustration] Kanban best practices (infographic)

1. Visualize work

One of the biggest advantages of Kanban is that you can physically see work “move” through stages. Not only does this practice give you a broad sense of how work moves through stages, but you can also get real-time, at-a-glance insight into the stage of work.

Create a Kanban card template

2. Limit work in progress

As an Agile methodology, Kanban is built on a principle of early delivery—which means tasks should move quickly between columns instead of languishing with an ambiguous “in progress” status. There’s no set requirement for how many tasks should be “in progress” at any given time, but in general, encourage your team to reduce multitasking and focus on the production of individual work.

3. Manage flow

Practice #2 states that you want to limit work in progress—and the best way to do that is to optimize the flow of tasks within your Kanban board. Managing and improving your flow will decrease your lead time (the amount of time spent between starting on a task and moving it to the “Done” column on your Kanban board), and ensure you’re delivering tasks or shipping new products while they’re still relevant.

4. Make process policies explicit

Because tasks move so quickly in Kanban, make sure your team has established and clearly communicated conventions. Your process policies should guide how your team implements the Kanban methodology.

Additionally, everyone on your team should be encouraged to participate and innovate on your Kanban policy, in accordance with the fourth Kanban core principle: Encourage acts of leadership at all levels.

5. Implement feedback loops

In Kanban, you want to gather feedback from two distinct groups: your customers and your team.

  • Customers: Gather feedback from customers on the quality and effectiveness of the solution your team produced. Was it the right thing to produce? Were there any problems? If there were problems (like bugs in code or defects in a product), revisit your Kanban flow and add more time for review, vetting, and evaluation.

  • Team: Check in frequently with your team on the process of running a Kanban framework itself. How do they feel about their output? Here you have another opportunity to encourage acts of leadership at all levels and improve your team’s process policies.

Feedback is an integral part of continuous improvement and therefore the Kanban framework.

6. Improve collaboratively, evolve experimentally

Kanban, at its core, is about continuous improvement. But this also means other systems might work well in conjunction with Kanban. Whether it’s Scrum or something else, always be willing to collaborate, experiment, and evolve your processes if necessary.

Kanban example

In accordance with the first Kanban core principle (start with what you do now), you can apply Kanban to any workflow. The best way to visualize a Kanban board is with a work management tool like Asana. In Asana, every project can be viewed in four ways, including a Kanban-style Boards View.

[Product UI] Customer feedback project example (Boards)
Free Kanban board template

No matter how you’re creating your Kanban board, follow these easy steps to apply Kanban to any of your existing processes:

1. Start with a blank board

Though your Kanban board will eventually hold all of your backlog tasks and completed work, it’s OK to start with a blank board for now. If you’re using a work management tool like Asana, make sure you’re on Boards View.

2. Create columns to represent work

Traditionally, Kanban board columns represent the various stages of work. The columns you create will depend on your team, but a few common columns include:

  • Backlog, Inbox, or New: This column is where new work will go before you assign it to a team member.

  • Ready or Prioritized: Move work into this column when it’s ready for kickoff.

  • In progress: This is work that your team is currently working on. You may break the “In progress” column into various other columns—for example, a content team might create columns for “Drafting,” “Reviewing,” and “Editing,” while an engineering team might have columns for “Development,” “Testing,” and “Deployment.”

  • On hold: Move work into this column if you have to block it for some reason.

  • Completed or Done: Move tasks into this column once they’re done!

3. Add tasks to represent work

[Product UI] Example engineering sprint task (Tasks)

In a Kanban board, each task is represented by a card. Make sure your task titles are actionable—we recommend starting them with verbs so your team knows exactly what they should be working on.

If you’re using a virtual work management solution, you can also add additional information, context, and files to Kanban task cards. Then, use tags to track metadata—like how much time the task should take or what the priority is.

Create a Kanban card template

4. Move work through stages

A core element of workflow management with Kanban boards is moving work through stages. You can do this manually by dragging and dropping tasks, or look for a virtual work management solution that automates this work for you.

For example, with Asana, you can set rules to automatically route work into different columns based on relevant task information, like moving a task into the “In progress” column once you’ve assigned it to a team member.

Automate work with Asana

5. Create new Kanban boards if necessary

You could theoretically use the same virtual Kanban board indefinitely. Because Kanban boards track work through a continuous process, there’s no required reason for you to ditch your current board.

But in some systems, like Scrum, you’ll be creating Kanban boards frequently for each new sprint. Simply create the new board—or erase your whiteboard—transfer over your task backlog, and get started on your work once again.

Kanban boards: Pros and cons

So now that you know how Kanban works, only one question remains: Should your team use Kanban? There’s no right or wrong answer—but here are some benefits and some downsides your team may experience with the Kanban framework.

The benefits of Kanban

Kanban is a great, flexible tool that can help teams balance work with team capacity. When done right, Kanban can:

  • Provide at-a-glance insight into your team's work. As a form of visual project management, Kanban can help you bring tasks to life and gain clear insight into your team’s workflows.

  • Increase clarity, especially for remote teams. If your team is working remotely, it can be difficult to gain visibility into what everyone is working on. By centralizing work and reducing the amount of work in flight at any given time, Kanban boards can help you and your team gain instant insight into who’s working on what.

  • Encourage flexibility. Because the Kanban framework is built on a process of continuous improvement, teams that implement Kanban can become more flexible and dynamic over time. If you follow the four core principles and the six key practices, your team can become more agile and open to change.

The downsides of Kanban

Kanban isn’t the right framework for every team. Some downsides of Kanban include:

  • It’s not as common among non-engineering teams. Like Scrum, Agile, and other lean methodologies, Kanban isn’t as well known among non-engineering teams. Kanban can be an effective tool for all sorts of teams. But if you’re planning to introduce a Kanban process to a non-engineering team, consider moving one workstream into Kanban at a time to help your team with the adoption process.

  • It can quickly become overwhelming. Because each task card takes up so much visual space, your Kanban board can quickly get cluttered and overwhelming if you have too many things in flight at once.

Visualize your team’s work

With Kanban boards, your team has a clear line of sight into the tasks everyone is working on and where those tasks are in the process. If you’re ready to try a Kanban board for your team, try Asana.

[Product UI] Hiring pipeline project example (Boards)

You can view any Asana project in four ways, including Boards View—a Kanban-style board that helps your team more easily visualize and navigate workflow.

Free Kanban board template

Related resources

Webinar

How Asana uses Asana for IT and technical program management