Kanban Method in Project Management: A PMP Exam Perspective

What Is the Kanban Method?

Kanban is an agile method focused on continuous flow rather than fixed-length iterations. Originating from Toyota's manufacturing system, Kanban has been adapted for knowledge work and software development. Unlike Scrum, which prescribes specific roles and time-boxed sprints, Kanban emphasizes visualizing work, limiting work in progress (WIP), and managing flow.

For PMP candidates, understanding Kanban is important because the exam tests your ability to select and apply the right approach for a given situation. Some projects are better suited to Kanban's flow-based model than to Scrum's sprint-based model.

The Six Core Practices of Kanban

1. Visualize the workflow — Use a Kanban board to make all work visible. Columns represent stages (e.g., To Do, In Progress, Review, Done).
2. Limit work in progress (WIP) — Set explicit limits on how many items can be in each stage simultaneously. This prevents overloading and exposes bottlenecks.
3. Manage flow — Monitor how work moves through the system. Look for smooth, predictable flow rather than bursts of activity followed by idle time.
4. Make policies explicit — Everyone should understand the rules: when does an item move from one column to the next? What does "done" mean for each stage?
5. Implement feedback loops — Regular cadences for reviewing the system's performance, such as daily standups, delivery planning meetings, and operations reviews.
6. Improve collaboratively, evolve experimentally — Use models and the scientific method to propose and test changes to the process.

WIP Limits: The Heart of Kanban

WIP limits are what make Kanban more than just a task board. Without WIP limits, a Kanban board is simply a to-do list visualization. With them, the board becomes a flow management system.

When a WIP limit is reached in a column, no new work can enter that stage until existing work moves forward. This forces the team to focus on completing work rather than starting new work — a powerful shift in mindset.

Why WIP Limits Matter for the PMP Exam

PMI may present scenarios where a team is overwhelmed with multitasking or where work keeps starting but nothing finishes. The correct response often involves implementing or enforcing WIP limits. Recognize that WIP limits reduce context switching, expose bottlenecks, and improve throughput.

Kanban Metrics

Kanban uses specific metrics to measure and improve flow:

• Lead Time — The total time from when a request is made to when it's delivered. This is the customer's perspective.
• Cycle Time — The time from when work begins on an item to when it's completed. This is the team's perspective.
• Throughput — The number of items completed per unit of time.
• Work Item Age — How long an in-progress item has been in the system.

These metrics help project managers identify trends, predict delivery dates, and spot process problems.

When to Use Kanban vs. Scrum

The PMP exam may test your judgment about when each approach is appropriate:

• Choose Kanban when work arrives unpredictably (support teams, maintenance), when you need continuous delivery rather than batch delivery, or when the team resists prescribed roles and ceremonies.
• Choose Scrum when you need regular delivery cadences, when the team benefits from structured events like retrospectives, or when you're building a complex product with a dedicated team.
• Combine them — "Scrumban" uses Scrum's structure with Kanban's WIP limits and flow visualization.

Kanban on the PMP Exam: Key Takeaways

Remember these points for exam day: Kanban is about flow, not iterations. WIP limits are essential, not optional. Kanban starts with your current process and improves incrementally — it doesn't require a radical overhaul. And Kanban metrics (lead time, cycle time, throughput) are practical tools for managing project performance.

Explore more agile methods and how they appear on the PMP exam in our topics library.