HKSM

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.