Kanban teams use which practices to manage flow?

Kanban teams use which practices to manage flow?

• A. Cycle time, lead time, small batch size, and throughput.
• B. Velocity and capacity.
• C. Burn-down charts and velocity.
• D. Iteration sprints and epics.

Answer: (A)

Managing flow in Kanban centers on metrics that show how work moves through the system. Cycle time and lead time measure how long items spend in the process—cycle time from when work starts to completion, lead time from request to delivery. Small batch size helps prevent bottlenecks by limiting work in progress, making it easier for items to flow smoothly. Throughput indicates how many items are completed in a given period, helping teams forecast and improve delivery rates. Together, these practices give a clear view of flow, highlight bottlenecks, and drive continuous improvement without fixed iteration cycles. Velocity and capacity, burn-down charts and velocity, and iteration sprints with epics align more with Scrum planning and sprint-based practices, not Kanban’s continuous flow focus.

Managing flow in Kanban centers on metrics that show how work moves through the system. Cycle time and lead time measure how long items spend in the process—cycle time from when work starts to completion, lead time from request to delivery. Small batch size helps prevent bottlenecks by limiting work in progress, making it easier for items to flow smoothly. Throughput indicates how many items are completed in a given period, helping teams forecast and improve delivery rates. Together, these practices give a clear view of flow, highlight bottlenecks, and drive continuous improvement without fixed iteration cycles.

Velocity and capacity, burn-down charts and velocity, and iteration sprints with epics align more with Scrum planning and sprint-based practices, not Kanban’s continuous flow focus.