A Brief Peek in the World of Kanban

Our daily lives have become so chaotic that it is easy to lose track of time and get almost nothing done. To obtain the most of each minute; we’ve often been told to make a task list like buying groceries, paying bills, cleaning the wardrobe, completing that pending blog, and so much more.

This art of creating a task list help in de-cluttering the work and gets the job done faster. And the agile methodology of Kanban revolves around the same idea.

It is a half-century-old concept; back in the early 1940s when Taiichi Ohno (Industrial Engineer and Businessman) for Toyota automotive in Japan got inspired by the product restocking system adopted at departmental stores in the United States of America.

Although Kanban was originally meant for better stock management at production facilities; the world of IT tweaked and utilized it as a means for project management.

This type of agile software development works on the principles of matching the backlog and the WIP with the team’s capacity, thereby effectively reducing the idle time.

It works on the pull-system, which means that the team can pick the task from the backlog as and when the work in hand gets finished.

All the work items are displayed on a kanban board which can be accessed by all the team members, and they can view the task status anytime.

This agile methodology is successful only in a transparent work environment backed by real-time communication amongst the members.

Components of Kanban

The Kanban has three main components, which are: The Kanban Board, Kanban Card, and Kanban WIP limit.

All three work together and give a detailed project overview to the Project Manager and the team.

  • Kanban Board

We all have designed a task list with three basic columns:

(will)Do > Doing > Done!

The task list depicts a kanban board at its most basic form wherein a workflow process is defined; it can be as simple as the above three-steps or complex depending upon the project.

It helps the team to visualize work and maximize their efficiency. Shown below is a commonly used sample of a kanban board by organizations throughout the world.

  • Kanban Card

Kanban cards in the kanban board are like sticky notes on a task list, which is moved from one column to another based on the status like to-do, under progress or done. In the kanban agile methodology, each card represents a user story.

Team members with access to the kanban board can add, edit, move, and delete cards from it. There is also an option to mark cards with colored labels based on their priority.

The team drives the card from one workflow to another based on the task development mentioned in the card. It furnishes a complete overview and standing of assignments in a project.

  • Kanban WIP Limits

WIP limit in a kanban represents the maximum number of cards that can be placed below a workflow at any point in time.

Imposing this limit eliminates the practice of multitasking undertaken by team members; enabling them to focus on one job at a time, get it done, and then move ahead with the next task. Setting a WIP limit increases the number of tasks done, and also highlight bottlenecks in the workflow.

Kanban versus Scrum

Your presence here is a sign that you are aware of or at least have an idea about the Scrum.

Both are different types of agile methodologies used for better project management, and have the following variations:

Over To You

It won’t be wrong to say that Kanban is one of the most popular and widely used methods of agile software development. But nowadays more and more IT companies are opting Scrumban; the hybrid of Kanban and Scrum.

In this technique, the company adopts Scrum to execute the work and Kanban as the lens to view areas for improvement. But whether opted alone or as hybrid, agile methodologies are paving the way for the future of software development.

By now you are aware of the use of Kanban in agile software development, but there is still a gap when it comes to prioritizing work. On what basis a task should be selected and completed first?

Well, the answer is the MoSCoW technique. If you wish to know more about this super cool task prioritization technique, then watch out this space for our next write-up explaining MoSCoW in detail.




Sarvika is a global technology solutions provider that started with a small team and spread its wings to a large team of developers, analysts and designer. Yes! while writing codes, we often feel our experiences and software industry’s know-how can benefit others too. Therefore,

Recommended from Medium

Unreal Engine 4 Animation Slot


Using Crossplane in GitOps: What to Check in Git

Julia Quickstart

How I Help Developers Sleep at Night

basic characteristics of a distributed database

Python: Min() Function Tutorial

Moving Calm to Microservices

AWS: CloudFormation — using Conditions, Fn::Equals, and Fn::If — an example

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Mehul Kumar

Mehul Kumar

Experienced Digital Marketer with a demonstrated history of working in the Content Marketing, Ecommerce and PR industry.

More from Medium

How to introduce Kanban to your team?

A man moving post-it notes on a wall Kanban board.

What is a Spike in Scrum?

3 ways to guide the business through “Project Chaos”

5 simple tips for better Product Backlog Refinement and a more effective Sprint Planning