What Is Kanban Method in Project Management?
Also known as: Kanban Method, Kanban definition, Kanban vs Scrum, Kanban PMP exam, Kanban WIP limit
On This Page
Quick Definition
Kanban is a way to manage work by making it visible on a board. You use columns to show where each task is in your process, like To Do, Doing, and Done. The main rule is that you don't start new work until you finish something already in progress. This keeps the team from getting overloaded and helps things move smoothly.
Must Know for Exams
The Kanban Method appears in the PMP certification exam primarily through the Agile Practice Guide, which is one of the reference materials for the exam. The PMP exam now includes a significant portion of questions on agile and hybrid approaches, and Kanban is a key agile framework covered in that domain. According to the PMP Examination Content Outline, about 50% of the exam covers the People domain, 25% covers the Process domain, and 25% covers the Business Environment domain. Kanban is most relevant to the Process domain, specifically in the area of managing the flow of work.
Exam candidates should know the core principles of Kanban: visualize the workflow, limit work in progress, manage flow, make policies explicit, implement feedback loops, and improve collaboratively. These principles may appear in questions that ask about techniques to reduce bottlenecks or improve throughput. For instance, a scenario might describe a team that is constantly overworked and unable to complete tasks on time. The correct answer would be to implement WIP limits and use a Kanban board to visualize the workflow.
The PMP exam also tests the difference between Kanban and other agile frameworks, particularly Scrum. Candidates must know that Kanban does not have fixed iterations (sprints), does not prescribe specific roles, and uses a continuous flow model rather than a time-boxed one. Questions may present a scenario where a team needs to respond quickly to changing priorities, and the best approach is Kanban because it allows work items to be reprioritized at any time.
Another common exam topic is the use of metrics in Kanban. Lead time and cycle time are frequently tested. A question might ask which metric helps predict when a work item will be completed, and the answer is cycle time, because it measures the time from when work starts until it is finished. Cumulative flow diagrams are also tested, as they provide a visual representation of work in progress and can help identify bottlenecks.
The PMI Agile Certified Practitioner (PMI-ACP) exam covers Kanban in even greater depth, but the PMP exam includes it as part of the agile and hybrid content. For both exams, candidates should understand how Kanban can be integrated with traditional project management. For example, a hybrid approach might use Gantt charts for high-level planning and Kanban boards for day-to-day task management.
Finally, exam questions may ask about the origin and philosophy of Kanban. Knowing that it originated in the Toyota Production System and was adapted for knowledge work by David J. Anderson can help answer questions about lean principles and continuous improvement. The key takeaway for exam success is to understand Kanban as a flow-based system that emphasizes pulling work based on capacity, not pushing work based on demand.
Simple Meaning
Imagine you are in a busy kitchen making sandwiches for a lunch rush. You have a counter where orders come in, a griddle where you cook, and a serving station where you hand out finished sandwiches. If you take every order that comes in and pile them on the griddle, you will quickly run out of space, burn some sandwiches, and make customers wait a long time. Kanban is a way to prevent this chaos.
In its simplest form, Kanban uses a board with columns. Each column represents a step in your work process. For example, a software team might use columns like Backlog, Analysis, Development, Testing, and Done. Each task is written on a card and placed in the first column. As work progresses, the card moves from left to right.
The most important idea in Kanban is limiting how many tasks can be in a column at one time. This is called a Work In Progress (WIP) limit. If the Development column has a limit of three cards, and there are already three cards in it, you cannot move a new card into Development until one of those cards moves forward. This forces the team to finish what they start before taking on new work.
Kanban is not a rigid methodology like some project management frameworks. It does not prescribe fixed time boxes or specific roles. Instead, it is a set of principles and practices that you apply to your existing workflow. The goal is to make bottlenecks visible, reduce waste, and improve the flow of value to the customer. It started in manufacturing at Toyota, but today it is used by software teams, IT operations, marketing departments, and many other areas.
Think of Kanban like a highway on-ramp with a merge lane. If too many cars try to merge at once, traffic slows to a crawl. But if you limit the number of cars entering the highway (your WIP limit), traffic flows more freely. Kanban gives you the tools to see where traffic jams are happening and fix them. It is about continuous improvement, not a one-time change.
Full Technical Definition
The Kanban Method is a workflow management framework designed to help teams optimize their delivery processes by visualizing work, limiting work in progress (WIP), and enhancing flow. It originated from Taiichi Ohno's just-in-time manufacturing system at Toyota and was later adapted for knowledge work by David J. Anderson in 2004. The method is based on four core principles: start with what you do now, agree to pursue incremental change, respect current roles and responsibilities, and encourage acts of leadership at all levels.
At the heart of Kanban is the Kanban board, which represents the workflow as a series of columns. Each column corresponds to a stage in the value stream. Work items are represented as cards on the board. The board can be physical (whiteboard with sticky notes) or digital (using tools like Jira, Trello, or Azure Boards). The columns are typically labeled with process stages such as To Do, In Progress, Review, and Done, but teams customize them to match their actual process.
A critical technical component is the WIP limit. Each column has a maximum number of work items allowed at any given time. When a column reaches its WIP limit, the team must focus on completing items in that column before pulling in new items from the previous column. This creates a pull system, as opposed to a push system where work is assigned regardless of capacity. The pull system prevents bottlenecks and reduces multitasking.
Kanban also incorporates metrics for process improvement. Lead time is the total time from when a work item is requested until it is delivered. Cycle time is the time from when work actually starts on an item until it is delivered. Teams use cumulative flow diagrams to visualize stability and identify bottlenecks. A control chart can show cycle time trends and help predict future delivery dates. These metrics support data-driven decisions about process changes.
In IT environments, Kanban is often used for software development, IT operations, and support ticket management. For example, an IT help desk might use a Kanban board to track incident tickets. Columns could include New, Assigned, In Progress, Awaiting User Response, and Resolved. WIP limits prevent technicians from taking on too many tickets at once, ensuring each issue gets timely attention. The board provides transparency to stakeholders about the status of all open tickets.
Kanban does not prescribe specific roles like Scrum Master or Product Owner. Instead, it encourages teams to manage their own workflow. A service delivery manager may act as a coach, but the team collectively decides how to improve. Regular cadences, such as daily standups and service delivery reviews, help the team inspect and adapt their process. Kanban is often combined with other frameworks; for instance, a team might use Scrum events but manage their work with a Kanban board, a hybrid known as Scrumban.
Real-world implementation requires careful board design. Teams must map their actual workflow, not an idealized version. Columns should reflect real handoffs and approvals. WIP limits must be realistically set based on team capacity, then adjusted over time. Digital Kanban tools provide analytics that allow teams to monitor lead time, cycle time, and throughput. These metrics enable evidence-based conversations about process improvement during retrospectives.
Kanban is recognized by the Project Management Institute (PMI) as a valid agile approach for project management. It is relevant to the PMP exam because it aligns with the Agile Practice Guide and the PMBOK Guide's emphasis on adaptive planning and continuous improvement. Understanding Kanban principles helps PMP candidates answer questions about managing work flow, reducing waste, and increasing predictability in agile environments.
Real-Life Example
Think about a public library that lends books. The library has a process for handling returned books so they can be borrowed again. When you return a book, it goes into a bin. A library assistant takes the bin to a sorting station where they check for damage. Then it goes to a reshelving cart. Finally, a shelver puts it back on the shelf. This is a multi-step workflow.
Now imagine there is no limit on how many books can be in the sorting station at one time. Returns pile up, and the sorting station becomes a mountain of books. The reshelving cart stays empty because nothing gets through sorting. Librarians cannot find books that are actually available, and patrons wait longer. This is exactly what happens in a work process without WIP limits.
Kanban would fix this library by putting limits at each step. The sorting station might have a limit of 20 books. Once 20 books are there, the assistant must stop taking books from the return bin until some are sorted and moved to the reshelving cart. The reshelving cart might have a limit of 10 books. When the cart is full, the sorter cannot send more books until the shelver clears some space.
The library also uses a visual board. A whiteboard at the service desk shows three columns: Returns, Sorting, and Shelved. Each column shows how many books are at that stage. Everyone can see that sorting is full, so the manager knows to ask why sorting is slow. Maybe there is only one sorter working, or the sorting takes longer because damaged books need repair. The library can then add a sitter or change the process to repair books after hours.
This analogy maps directly to Kanban in IT. The library board is like a Kanban board. The columns are workflow stages. The limits are WIP limits. The books are work items (features, bugs, tickets). The goal is to find and fix bottlenecks so that work flows smoothly from start to finish. By making the process visible and limiting work in progress, the library delivers books back to patrons faster and with less chaos.
Why This Term Matters
Kanban matters in real IT work because it addresses the most common productivity killer: overload. IT professionals constantly juggle multiple tasks, urgent support tickets, feature requests, and maintenance work. Without a system to control how much work enters the pipeline, teams become reactive, context switching explodes, and quality suffers. Kanban provides a structured way to manage this complexity.
For system administrators and IT operations teams, Kanban helps manage incident response. When a server goes down, tickets pour in. Without WIP limits, a single admin might start working on three incidents at once, resolving none quickly. Kanban forces the admin to finish one incident before picking up the next. This reduces mean time to resolution and prevents mistakes from rushed work.
For software developers, Kanban improves feature delivery. Instead of starting development on ten features and finishing none, the team commits to a small number and completes them before taking on more. This predictable flow means stakeholders see finished work regularly, not just promises. It also reduces the risk of delivering half-finished features that never see the light of day.
Kanban matters in cloud infrastructure management as well. Cloud engineers often manage dozens of tasks from provisioning VMs to configuring load balancers. A Kanban board shows which tasks are blocked by missing approvals or dependencies. This visibility allows engineers to unblock high-priority work quickly and communicate status to managers without constant status meetings.
In cybersecurity, Kanban can track vulnerability remediation. Each vulnerability is a work item that moves from discovered, through analysis, patching, and verification. WIP limits ensure the security team does not start too many patches at once, which could introduce instability. The board shows which critical vulnerabilities are still open at a glance, helping the team prioritize effectively.
Kanban is not just for teams; it is useful for individual IT professionals managing their own work. A personal Kanban board can track tasks across personal projects, certification study, and work responsibilities. It helps individuals see where they are spending time and where they are getting stuck. This self-awareness leads to better time management and reduced stress.
Ultimately, Kanban matters because it is a lightweight, low-risk improvement method. You do not need to change your entire process overnight. You start with your current workflow, add a visual board, and set initial WIP limits. As you see bottlenecks, you make small adjustments. This continuous improvement mentality is essential for IT environments that must adapt quickly to changing demands.
How It Appears in Exam Questions
Kanban appears in certification exam questions in several distinct patterns. The most common pattern is the scenario question that describes a team experiencing workflow problems. For example, the question might say: A software development team is frequently overwhelmed with work. Developers are context-switching between multiple features, and nothing gets completed on time. What practice should the team adopt? The correct answer is to implement a Kanban system with WIP limits. These questions test your ability to diagnose symptoms of overload and prescribe the right solution.
Another pattern is the comparison question that asks you to distinguish Kanban from other methods. For instance: Which of the following is a characteristic of the Kanban Method, but NOT of Scrum? The answer choices might include fixed-length iterations, WIP limits, defined roles, or daily standups. The correct answer is WIP limits, because Kanban emphasizes limiting work in progress, while Scrum does not inherently include WIP limits. These questions require precise knowledge of Kanban's unique attributes.
Definition questions ask for the meaning of key Kanban terms. For example: What is the definition of a pull system in Kanban? The answer: A system where work items are moved to the next stage only when there is capacity to handle them, as opposed to pushing work regardless of capacity. Similarly, you might be asked to define lead time versus cycle time, or to interpret a cumulative flow diagram.
Scenario questions may also present a specific situation with a Kanban board. The question might show a board with columns and WIP limits, then ask: What is the most likely issue if the board shows all items stuck in the Testing column? The answer: The Testing column has reached its WIP limit, or there is a bottleneck in testing. You must read the board and identify the bottleneck based on where work is piling up.
Troubleshooting questions ask you to fix a failing Kanban implementation. For example: A team implemented Kanban but still experiences frequent delays. Upon inspection, the board shows that the Development column rarely exceeds its WIP limit, but the Review column is always full. What should the team do? The answer: Increase capacity in the Review stage, for example by assigning more reviewers or reducing the review backlog.
Finally, there are questions about Kanban within the context of larger project management. A question might describe a project using a hybrid approach, with a predictive plan for the overall timeline but a Kanban board for execution. The question may ask: What benefit does the Kanban board provide in this hybrid environment? The answer: It provides real-time visibility into work progress and helps the team manage day-to-day tasks while staying aligned with the high-level plan. Expect these questions to test both conceptual understanding and practical application.
Study pmi-pmp
Test your understanding with exam-style practice questions.
Example Scenario
A small IT support team of three people handles help desk tickets for a company with 200 employees. They receive about 20 new tickets each day. In the past, each technician would grab whichever ticket they felt like working on, often starting multiple tickets at once. Customers complained about slow response times, and tickets would sometimes get lost for days.
The IT manager decides to implement Kanban. They set up a physical whiteboard in the office with four columns: New, In Progress, Awaiting Customer Response, and Closed. Each ticket is written on a sticky note and placed in the New column when it arrives. The manager sets a WIP limit of 2 for the In Progress column. This means each technician can only have two tickets active at a time. If a technician already has two tickets in In Progress, they must finish or reassign one before taking a new ticket from the New column.
Within a week, the team notices improvement. Technicians no longer feel overwhelmed because they are forced to finish tickets before starting new ones. The board shows clearly which tickets are waiting for customer input, so the team follows up with those customers proactively. The manager can see at a glance when the In Progress column is full, indicating that the team is at capacity and new requests will have to wait. This visibility helps the manager communicate realistic timelines to stakeholders.
Over time, the team adds a fifth column called Urgent for critical issues like server outages. They set a separate WIP limit for urgent items to ensure quick response. The team holds a weekly 15-minute review to discuss flow and adjust WIP limits based on recent trends. After three months, average resolution time drops from 48 hours to 18 hours, and customer satisfaction scores improve significantly. This scenario shows how a simple Kanban implementation can transform team performance without requiring expensive tools or major process changes.
Common Mistakes
Thinking Kanban is only for manufacturing and not for IT or knowledge work.
Kanban was originally developed for manufacturing, but it has been successfully adapted for software development, IT operations, marketing, and other knowledge work fields. The principles of visualizing work, limiting WIP, and managing flow are universal.
Understand that Kanban is a general-purpose workflow management method. It works wherever there is a process with steps and handoffs, regardless of industry.
Believing that Kanban has fixed iterations or sprints like Scrum.
Kanban is a continuous flow system. It does not have time-boxed iterations. Work items are pulled through the process as capacity allows, not at the start of a sprint. This is a key differentiator.
Remember that Kanban is flow-based, not time-boxed. The only rhythm in Kanban is the regular cadence of review and improvement meetings, not fixed delivery intervals.
Setting WIP limits too high or too low without adjustment.
If WIP limits are set too high, the board effectively has no limits and the team stays overloaded. If set too low, the team may be underutilized or unable to handle normal workload. The correct approach is to set initial limits based on historical capacity and then adjust based on observed flow.
Start with a WIP limit equal to the number of team members in a column, then gradually lower the limit until you find the sweet spot where work flows smoothly without bottlenecks.
Treating the Kanban board as a task assignment tool rather than a flow management tool.
The purpose of the board is to visualize the flow of work and identify bottlenecks, not to assign tasks to specific people. The team collectively manages the board and decides who pulls which card based on capacity.
Use the board to see where work is piling up, then have the team discuss how to resolve the bottleneck. Let team members pull work from the board when they have capacity, rather than having a manager push tasks onto them.
Ignoring the explicit policies that govern how work moves between columns.
Kanban requires making rules explicit, such as what qualifies a work item to move from In Progress to Review. Without explicit policies, team members may move items prematurely or inconsistently, leading to confusion.
Write down the definition of done for each column. Post it next to the board so everyone understands the criteria for moving cards. Review and update these policies regularly as the process evolves.
Exam Trap — Don't Get Fooled
A question describes a team using a Kanban board but also having daily standups and a product owner, and asks what framework they are using. Some choices will say Scrum and others will say Kanban. The trap is that having daily standups and a product owner does not automatically mean Scrum, because Kanban teams can also have daily standups and a service request manager acts similarly to a product owner.
Focus on the defining characteristics: does the scenario mention time-boxed iterations (sprints)? If yes, it is Scrum. Does it mention WIP limits and continuous flow? If yes, it is Kanban.
Standups and a product owner are not exclusive to either framework, so do not use them as deciding factors.
Commonly Confused With
Scrum uses fixed-length sprints (typically 1-4 weeks) with a defined set of work committed at the start, while Kanban uses continuous flow with no fixed iterations. Scrum has prescribed roles (Product Owner, Scrum Master, Development Team), while Kanban does not prescribe specific roles. Scrum is a framework; Kanban is a method for improving flow that can be applied on top of any process.
A team that plans work in two-week sprints and holds sprint reviews is using Scrum. A team that moves cards through a board continuously with no sprint boundaries is using Kanban.
Lean is a broader philosophy focused on eliminating waste and maximizing value, originating from the Toyota Production System. Kanban is one of the tools used within Lean to achieve those goals. You can practice Lean principles without using Kanban, and you can use Kanban without fully adopting Lean philosophy.
Lean is the overall mindset of reducing waste like unnecessary meetings or handoffs. Kanban is the specific board and WIP limits that help visualize and control the flow of work.
Waterfall is a sequential, phase-gated approach where each phase must be completed before the next begins (e.g., requirements before design before development). Kanban is iterative and allows work items to move independently through stages. Waterfall is predictive and plan-driven; Kanban is adaptive and flow-driven.
In Waterfall, you write all requirements first, then hand them to developers. In Kanban, you pull a small requirement, develop it, test it, and deliver it before picking up the next requirement.
Step-by-Step Breakdown
Visualize the Workflow
The first step is to map your current process as columns on a board. Each column represents a stage in your work flow, such as Backlog, Development, Testing, and Done. Every work item, whether it is a feature, bug, or support ticket, is written on a card and placed in the appropriate column. This makes the invisible work visible to everyone on the team and to stakeholders.
Limit Work in Progress (WIP)
Set a maximum number of work items allowed in each column. For example, you might set a WIP limit of 3 for the Development column. When a column reaches its limit, no new items can enter that column until one leaves. This forces the team to finish existing work before starting new work, reducing multitasking and highlighting bottlenecks.
Manage Flow
Once the board is set up and WIP limits are in place, the team monitors how work moves from left to right. They pay attention to lead time and cycle time. If work is piling up in a particular column, that is a signal that the column is a bottleneck. The team discusses why the bottleneck exists and takes action, such as allocating more resources to that stage or changing the process.
Make Policies Explicit
The team writes down the rules that govern how work moves between columns. For example, a policy might state that a work item can only move from Development to Testing if all unit tests pass and a code review has been completed. Having explicit policies reduces ambiguity and ensures everyone follows the same criteria when moving cards.
Implement Feedback Loops
Kanban includes regular cadences for the team to review their process. Common feedback loops include a daily standup to discuss the board and any blockers, a service delivery review to show metrics to stakeholders, and a recurring operations review to analyze longer-term trends. These meetings are short and focused on improving flow, not on status reporting.
Improve Collaboratively
The final step is to use the insights from the board and feedback loops to make incremental improvements. The team experiments with changes, such as adjusting WIP limits, adding a new column, or changing a policy. The improvement is based on data, not opinions. The team measures the impact of each change and decides whether to keep it or try something else.
Practical Mini-Lesson
Kanban is not just a board with sticky notes. It is a strategy for managing change and improving how work gets done. To implement Kanban successfully in an IT environment, you need to start with your existing process, not a theoretical ideal. Begin by mapping your current workflow. If you are a help desk team, your stages might be New Ticket, Assigned, In Progress, Awaiting User, and Resolved. If you are a development team, your stages might be Backlog, Analysis, Development, Code Review, Testing, and Deployed. The board must reflect reality, even if that reality includes messy handoffs or manual approvals.
Once the board is built, set initial WIP limits. A good starting point is the number of people working in a column. For a three-person development team, set a WIP limit of 3 for Development. Then monitor the board for a week. If cards move smoothly and the column never reaches the limit, the limit is too high. Lower it to 2 and observe again. If cards pile up and never move, the limit is too low or there is a bottleneck elsewhere. Adjust iteratively.
Professionals must also understand that Kanban is not about doing more work. It is about finishing what matters. By limiting WIP, you reduce the time each task spends waiting. This decreases lead time and makes delivery more predictable. In practice, this means that stakeholders receive completed features more regularly, but they may need to wait slightly longer for a new feature to be started. The trade-off is worth it because completed work is better than partially done work that never ships.
What can go wrong? The most common failure is that the team ignores the WIP limits. When a manager pressures the team to start a new urgent task, the team might move cards into a column that is already full, breaking the system. To prevent this, the team must have the discipline to say no and the support of management to respect the limits. Another issue is that the board becomes outdated if the process changes but the board does not. Regular retrospectives ensure the board stays accurate.
Kanban connects to broader IT concepts like DevOps and continuous delivery. In DevOps, the goal is to move code from commit to production quickly and safely. Kanban provides the visibility and flow control to achieve this. A deployment pipeline is essentially a Kanban board for code, with stages like Build, Test, Staging, and Production. WIP limits prevent too many changes from being in the pipeline at once, reducing the risk of conflicts and deployment failures.
To succeed with Kanban, think of yourself as a flow manager, not a task assigner. Your job is to optimize the system so that work flows smoothly from start to finish. Measure lead time and cycle time regularly. Use cumulative flow diagrams to spot trends. Celebrate when cards move quickly, and investigate when they stall. Over time, small improvements compound into significant gains in speed, quality, and team morale.
Memory Tip
Kanban is like a kitchen with a full grill: you cannot add new food until you take cooked food off. WIP limits are your grill slots; they prevent you from burning everything by trying to cook too much at once.
Covered in These Exams
Related Glossary Terms
An A record is a DNS record that maps a domain name to the IPv4 address of the server hosting that domain.
Two-factor authentication (2FA) is a security method that requires two different types of proof before granting access to an account or system.
5G is the fifth generation of cellular network technology, designed to deliver faster speeds, lower latency, and support for many more connected devices than previous generations.
Frequently Asked Questions
Do I need special software to use Kanban?
No. You can start with a physical whiteboard and sticky notes. Many teams use digital tools like Jira, Trello, or Azure Boards, but the principles work the same with any visual board. Start simple and add tools only when needed.
Can Kanban be used with Scrum?
Yes. Many teams use a hybrid called Scrumban, where they keep Scrum events like sprints and standups but use a Kanban board with WIP limits to manage work within the sprint. This combines the structure of Scrum with the flow management of Kanban.
What is a WIP limit and how do I set it?
A WIP limit is the maximum number of work items allowed in a column at one time. Start with a limit equal to the number of people working in that column, then adjust based on observation. The goal is to keep work moving without piling up.
How is Kanban different from a to-do list?
A to-do list is just a list of tasks. A Kanban board shows the entire workflow, including where each task is in the process. It also enforces WIP limits, which a to-do list does not. Kanban gives you insight into bottlenecks and flow, while a to-do list only shows what remains to be done.
Does Kanban work for a single person?
Absolutely. Many individuals use a personal Kanban board to manage their own tasks. It helps visualize progress, limit multitasking, and focus on finishing important tasks before starting new ones. It is a great tool for studying for certification exams or managing freelance work.
What are the most important metrics in Kanban?
Lead time (time from request to delivery) and cycle time (time from start to delivery) are the key metrics. Throughput (number of items delivered per period) is also useful. These metrics help you measure whether your process is improving over time.
Can Kanban be used for non-software projects?
Yes. Kanban is used in marketing, HR, event planning, and many other fields. Any process with defined steps and handoffs can benefit from visualizing the workflow and limiting work in progress.
Summary
The Kanban Method is a powerful yet simple approach to managing work that emphasizes visualization, flow, and continuous improvement. By putting work items on a board with columns representing process stages and enforcing strict limits on how many items can be in each stage, teams can dramatically reduce overload, improve delivery speed, and increase predictability. Unlike other frameworks, Kanban does not require a major organizational change you start with your existing workflow and make incremental adjustments.
For IT certification candidates, especially those preparing for the PMP exam, understanding Kanban is essential because it appears in questions about agile practices, workflow management, and process improvement. Remember the core practices: visualize the workflow, limit work in progress, manage flow, make policies explicit, implement feedback loops, and improve collaboratively. Kanban is not just a tool for manufacturing it is a universal method that helps any team, including IT support, software development, and cloud operations, deliver value more efficiently.
When you encounter exam questions about reducing bottlenecks or improving team throughput, think of Kanban and the discipline of WIP limits. With practice, you will see that Kanban is less about moving cards and more about building a culture of continuous improvement.