September 7, 2026 · 6 min read
TL;DR: Kanban on the PMP exam is a system of four ideas working together: visualize the work, limit work in progress, manage flow with pull, and improve collaboratively. The questions test whether you can find the constraint. Across this bank's 84 flow questions the keyed answers repeatedly fix the thing causing the queue rather than adjust the board that displays it.
Kanban tends to get studied as a board. Columns, cards, maybe a number at the top of a column. That is the visible half, and it is the half the exam mostly does not ask about. What the questions actually test is whether you understand the board as an instrument that reveals a constraint, and whether you will act on the constraint when you find it.
Kanban has six core practices, usually taught as four paired ideas: visualize the workflow and limit work in progress, manage flow and enable pull, make policies explicit, and implement feedback loops with collaborative improvement.
One question asks a product owner new to agile which of four options is NOT a core property. Three options pair the practices correctly. The keyed answer, the one that is not Kanban, is "follow the procedures and never deviate from the plan." That is not a throwaway distractor. It names the exact opposite disposition: Kanban makes policies explicit precisely so they can be inspected and changed, and the feedback loops exist to change them.
The bank's explanation frames these as a system rather than a menu, which is the framing that answers most Kanban questions. Visualisation shows where work accumulates. A work in progress limit forces the accumulation to be dealt with instead of grown. Pull means capacity draws work rather than work being pushed at people. Remove any one and the others stop working.
The board is a measure of progress, not a task list, because every card sits somewhere and its position states how far that increment has travelled.
A question asks what the story cards on a Kanban board primarily serve as, where each card represents an increment of value. The keyed answer is a measure of progress. The distractors offer a driver of executive behaviour, a way to pay for the cost of an agile team, and an enabler of engagement. The reason the keyed answer wins is structural: because every card is somewhere, the board states the progress of the whole system at a glance, including what is done, what is in flight, what is waiting, and crucially where the queue is building.
That last part is the exam-relevant one. A board that shows a queue building is telling you where the constraint is, and the questions that follow ask what you do about it.
| Symptom on the board | What it means | Keyed direction |
|---|---|---|
| Work piling up in one column | The constraint sits at or after that column | Deal with the accumulation, do not raise the limit |
| Everything in progress, nothing done | Work in progress limit is absent or ignored | Limit the work, let capacity pull |
| Approvals queuing on one person | That person is the constraint | Delegate authority over defined areas |
| Work pulled but never finishable | The pull system has a gap in it | Close the gap before extending the system |
| Cards move but nobody knows the finish date | The board shows state, not rate | Use a rate and a remaining quantity |
Common trap: treating a full column as a staffing problem and reaching for the option that adds people or raises the limit. The board is showing you a constraint, and adding capacity upstream of a constraint makes the queue longer, not shorter. In this bank's flow questions, adding resources appears only as a distractor, never as a key.
Yes, and this is one of the most reliably keyed shapes in the whole flow slice: when work queues for one person's decision, that person is the constraint.
During a key phase of an infrastructure project, the project manager notices decision-making slowing because they personally must approve many minor adjustments, while their own schedule is consumed by stakeholder meetings. The options include holding weekly roundup sessions to clear all accumulated decisions at once, running a critical path analysis to confirm decision-making is the delay, and making every decision personally to keep them timely. The keyed answer is to delegate decision-making for specific areas to trusted project leads.
The reasoning maps directly onto flow thinking. The binding constraint is the project manager's availability rather than the team's competence, so delegating authority over defined areas removes the queue at its source. Batching decisions into a weekly session is the interesting wrong answer, because it looks like process improvement while still routing everything through one person and building delay in by design.
Fix the gap before you extend the system, because every group that adopts a broken pull mechanism inherits both the break and whatever stopgap is covering it.
An EV charging network operator is changing how faults get fixed. Instead of a call centre assigning every job, regional technicians pull work from a shared queue and plan their own routes, released one region at a time. After four weeks in the first region, a hole is visible: nothing in the queue lets one technician commit another to a job, so rapid-charger faults needing two people for high-voltage isolation went untouched until the control room began phoning round to pair technicians up. That dispatching role is the one the change removed, and rapid-charger faults now wait days. Two more regions switch in a fortnight and the sponsor does not want to lose momentum.
The keyed answer is to pause the remaining regions until the gap has been closed in the shared queue, then resume. This is not a first region struggling with something unfamiliar. The new way of working has a structural hole, and the only thing moving those jobs is a manual workaround that cannot scale to three regions. Letting each region choose its own switch date, backlogging the two-person jobs, or asking technicians to self-organize the pairing all leave the hole in place.
There is a related design idea the bank keys elsewhere. Asked which agile method makes quality everyone's responsibility by pooling skill sets and cutting reliance on outside inputs, the answer is the whole-team approach: assemble a team holding every skill the work requires, so an item can travel from idea to done without leaving the team. Handoffs are where queues form, so removing handoffs is a flow intervention even when the question never mentions Kanban.
These questions are more about reading a system than recalling a definition, which is the kind of skill that develops from working through scenarios where every wrong answer is explained rather than just marked wrong.
What are the core properties of Kanban on the PMP exam? Visualize the workflow and limit work in progress, manage flow and enable pull, make policies explicit, and implement feedback loops with collaborative improvement. One bank question keys following procedures and never deviating from the plan as the property that is NOT Kanban.
What does a work in progress limit actually do? It forces accumulated work to be dealt with rather than grown. Visualization shows where work piles up, the limit stops the pile from being extended, and pull means free capacity draws the next item instead of work being pushed into a queue nobody is clearing.
What is a Kanban board primarily for? Measuring progress. Each card is one increment of value, and its position states how far that increment has travelled, so the board states the progress of the whole system at a glance rather than serving as a task list.
Can the project manager be the bottleneck? Yes, and the bank keys that scenario directly. When minor adjustments queue for one person's approval, the constraint is that person's availability, and delegating authority over defined areas removes the queue at its source.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained, not just marked wrong, so you can see why raising a limit loses to clearing a queue across a run of flow scenarios. Start the free 20-question sample — no card, no signup required to try it.
What are the core properties of Kanban on the PMP exam?
Visualize the workflow and limit work in progress, manage flow and enable pull, make policies explicit, and implement feedback loops with collaborative improvement. One bank question keys following procedures and never deviating from the plan as the property that is NOT Kanban.
What does a work in progress limit actually do?
It forces accumulated work to be dealt with rather than grown. Visualization shows where work piles up, the limit stops the pile from being extended, and pull means free capacity draws the next item instead of work being pushed into a queue nobody is clearing.
What is a Kanban board primarily for?
Measuring progress. Each card is one increment of value, and its position states how far that increment has travelled, so the board states the progress of the whole system at a glance rather than serving as a task list.
Can the project manager be the bottleneck?
Yes, and the bank keys that scenario directly. When minor adjustments queue for one person's approval, the constraint is that person's availability, and delegating authority over defined areas removes the queue at its source.