How to Calculate Withdrawal Cards in Kanban System

Withdrawal cards in Kanban systems help teams manage work in progress and maintain a sustainable pace. Calculating withdrawal cards involves analyzing your team's capacity, work items, and workflow to determine how many items can be completed in a given period. This guide explains the process step-by-step with a built-in calculator.

What Are Withdrawal Cards?

Withdrawal cards are a Kanban technique used to limit work in progress (WIP) and prevent overloading teams. They represent the maximum number of work items a team can commit to at any given time. When a team reaches its withdrawal limit, they stop accepting new work until some items are completed.

Withdrawal cards help maintain a sustainable pace, reduce context switching, and improve flow efficiency. They're particularly useful for teams practicing continuous delivery or iterative development.

Why Calculate Withdrawal Cards?

Calculating withdrawal cards ensures your team operates at an optimal capacity. Key reasons to calculate withdrawal cards include:

Preventing team burnout by maintaining a sustainable workload
Improving flow efficiency and reducing cycle time
Enabling better forecasting and planning
Creating a visual representation of team capacity
Supporting continuous improvement initiatives

Accurate withdrawal card calculations help teams maintain balance between throughput and quality while adapting to changing workloads.

How to Calculate Withdrawal Cards

The calculation involves several key factors:

Determine your team's average velocity (number of items completed per cycle)
Calculate your team's capacity (available working hours per cycle)
Set your withdrawal limit based on these factors
Adjust for variability and buffer time

Withdrawal Limit = (Team Velocity × Cycle Time) + Buffer

Where:

Team Velocity = Average number of items completed per cycle
Cycle Time = Average time to complete one work item
Buffer = Additional items to account for variability (typically 20-30%)

Step-by-Step Calculation

Measure your team's velocity over several iterations (e.g., 3-5 sprints)
Calculate average cycle time for completed work items
Multiply velocity by cycle time to get base capacity
Add 20-30% buffer for variability
Round to the nearest whole number for practical application

Note: Withdrawal limits should be adjusted periodically as team velocity and cycle time change. Regular reviews help maintain optimal flow.

Example Calculation

Let's calculate withdrawal cards for a software development team:

Metric	Value
Team Velocity	5 items per sprint
Cycle Time	3 days
Buffer	25% (1.25 multiplier)

Calculation:

Withdrawal Limit = (5 items × 3 days) × 1.25 = 18.75 → Round to 19

This team should set a withdrawal limit of 19 items to maintain sustainable flow while accounting for variability.

FAQ

How often should withdrawal limits be recalculated?: Withdrawal limits should be reviewed at least every sprint or iteration, or whenever significant changes occur in team composition, workload, or process.
What if my team's velocity varies significantly?: Use historical data to calculate an average velocity, and add a larger buffer (25-30%) to account for variability. Regularly review and adjust as needed.
Can withdrawal limits be different for different work types?: Yes, teams can set different withdrawal limits for different types of work (e.g., features vs. bugs) based on their specific characteristics and priorities.
How do withdrawal cards differ from WIP limits?: Withdrawal cards are a visual representation of WIP limits. While WIP limits are a numerical constraint, withdrawal cards provide a physical or digital marker to help teams track and enforce their limits.
What happens if a team exceeds its withdrawal limit?: When a team reaches its withdrawal limit, they should stop accepting new work until some items are completed. This helps maintain flow and prevents overloading the team.