Kanban Method

An Agile approach derived from the original Kanban stock-control system, tailored for managing knowledge work.

Key Points

  • Visualizes work on a board with columns that reflect workflow states.
  • Limits work in progress (WIP) to reduce multitasking and expose bottlenecks.
  • Uses a pull-based system where new work is started only when capacity is available.
  • Optimizes continuous flow and improves using measures like lead time and cycle time.

Example

A software maintenance team manages incoming defects on a Kanban board with columns Backlog, Ready, In Progress, Review, and Done. The team sets WIP limits of 5 for In Progress and 3 for Review. When a developer finishes a task, they pull the next highest-priority item from Ready. The team tracks cycle time weekly and adjusts WIP limits to eliminate bottlenecks in Review.

PMP Example Question

A team wants to improve throughput without fixed-length iterations. They plan to visualize their workflow and cap how many items can be in progress at once. Which approach best fits their needs?

  1. Kanban Method
  2. Scrum with two-week sprints
  3. Critical Path Method
  4. Earned Value Management

Correct Answer: A — Kanban Method

Explanation: Kanban emphasizes visualizing work, limiting WIP, and managing flow without timeboxed iterations, making it the best fit.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Advance your Lean Six Sigma expertise!

HK School of Management helps you take Lean Six Sigma to the next level without the overwhelm. Master advanced statistical tools, Excel-based analysis, and real-world improvement techniques to solve complex problems with confidence. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More